Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
EOASkripts/doc/bibliography.md
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
25 lines (19 sloc)
1.01 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# How the bibliography is made | |
References are stored in a bibtex file. The XML file contains | |
citations that are similar to a LaTeX citation command. | |
During processing, the bibtex file and the bibliography and citation | |
type (anthology or monograph, numeric or author/year) are read out of | |
the XML source file. | |
`pandoc-citeproc` is used to construct a JSON file out of the bibtex | |
database. This is helpful during the next parts of processing. | |
<!-- | |
!-- What exactly is it used for? Just for putting the title in the popover element? | |
--> | |
The next step formats the bibliography, depending on the bibliography | |
type, as a complete list or as per-chapter-list. In the second case, | |
several markdown and html files are created, one for each chapter. | |
They are named after the `xml:id` of the chapter. | |
The function `format_citations` then creates two outputs: the list of | |
references, formatted in html and a dictionary with the citekey as | |
headword and three manifestations of the data (author-year-citation, | |
year-citation and title). |