diff --git a/ICHLL_Brenon.md b/ICHLL_Brenon.md
index 5e4d66451a6290e4d180a089f9c1374a319734fd..8aabd33e55b75d489bbfa31fe7ed2f1f4e3e7558 100644
--- a/ICHLL_Brenon.md
+++ b/ICHLL_Brenon.md
@@ -15,68 +15,72 @@ header-includes:
# Abstract {-}
As witnesses to scientific progress, dictionaries and encyclopedias draw much
-interest from digital humanities (Roe et al. (2016), Williams (2017), Vigier et
-al. (2019), …), which accounts for the number of projects making them available
-to the public (such as ARTFL[^ARTFL], ENCCRE[^ENCCRE], COLLEX-LGE[^LGE] and
-NENUFAR[^NENUFAR]) or studying them in diachrony (such as BASNUM[^BASNUM] and
-GEODE[^GEODE]).
-
-[^ARTFL]: [http://artfl-project.uchicago.edu/](http://artfl-project.uchicago.edu/)
-[^ENCCRE]: [http://enccre.academie-sciences.fr/encyclopedie/](http://enccre.academie-sciences.fr/encyclopedie/)
-[^LGE]: [https://www.collexpersee.eu/projet/disco-lge/](https://www.collexpersee.eu/projet/disco-lge/)
-[^NENUFAR]: [https://cahier.hypotheses.org/nenufar](https://cahier.hypotheses.org/nenufar)
-[^BASNUM]: [https://anr.fr/Projet-ANR-18-CE38-0003](https://anr.fr/Projet-ANR-18-CE38-0003)
-[^GEODE]: [https://geode-project.github.io/](https://geode-project.github.io/)
-
-The volume of data involved issues a technical challenge to the digitizing
-process required for the study of historical dictionaries. XML-TEI, a major
-standard, includes a specialized module for dictionaries but it has shown some
-limitations when used to encode «La Grande Encyclopédie», a late-19th century
-encyclopedia (Jacquet-Pfau (2015)) from an OCRized version in XML-ALTO.
-
-We describe those limitations and identify the fundamental differences that
+interest from digital humanities, which accounts for the number of projects
+making them available to the public or studying them. However, the volume of
+data involved issues a technical challenge to the digitizing process required
+for the study of historical dictionaries.
+
+The goal of project DISCO-LGE was to study a late-19^th^
+century encyclopedia, "La Grande Encyclopédie". Working from an OCRised version
+in XML-ALTO, we devised an encoding scheme suitable for an automatic tool to
+represent and structure the text of encyclopedias. XML-TEI, a major standard,
+includes a specialised module for dictionaries we hoped to be able to build on,
+but systematic traversal of the schema using graph search methods revealed some
+limitations when used to encode our corpus.
+
+We describe these shortcomings and identify the fundamental differences that
prevent encoding encyclopedias with the XML-TEI module for dictionaries. We then
propose alternative encodings for encyclopedias while discussing their
-advantages and drawbacks, including a fully XML-TEI-compliant scheme suitable
-for automated processes.
-
+advantages and drawbacks, including a fully XML-TEI-compliant scheme.
# Dictionaries and encyclopedias
-After emerging from dictionaries during the 18\textsuperscript{th} century,
-encyclopedias became a fertile subgenre in themselves and a rich subject of
-study to digital humanities for their particular relation to knowledge and its
-evolution.
-
-CollEx-Persée project DISCO-LGE[^LGE] set out to study *La Grande
-Encyclopédie, Inventaire raisonné des Sciences, des Lettres et des Arts par une
-Société de savants et de gens de lettres* and was published between 1885 and
-1902 by an organised team of over two hundred specialists divided into eleven
-sections. Its aim was to digitise and make *La Grande Encyclopédie* available to
-the scientific community as well as the general public. A previous version of
-this encyclopedia was partially available on Gallica[^Gallica] but lacked in
-quality and its text had not been fully extracted from the pictures with an
-Optical Characters Recognition (OCR) system.
+After emerging from dictionaries during the 18^th^ century, encyclopedias became
+a fertile subgenre in themselves and a rich subject of study to digital
+humanities for their particular relation to knowledge and its evolution. In this
+section we will describe the goal of our project, then look at the origin of the
+term "encyclopedia" itself before comparing the approaches of encyclopedias and
+dictionaries.
+
+## Context of the project
+
+CollEx-Persée project DISCO-LGE[^LGE] set out to study *La Grande Encyclopédie,
+Inventaire raisonné des Sciences, des Lettres et des Arts par une Société de
+savants et de gens de lettres*, an encyclopedia published in France between 1885
+and 1902 by an organised team of over two hundred specialists divided into
+eleven sections. This text comprises 31 tomes of about 1200 pages each and
+according to @jacquet-pfau2015 was the last major french encyclopedic endeavour
+directly inheriting from the prestigious ancestor that was the *Encyclopédie ou
+Dictionnaire raisonné des sciences des arts et des métiers* published by Diderot
+and d'Alembert 130 years earlier, between 1751 and 1772.
-[^Gallica]: [https://gallica.bnf.fr/services/engine/search/sru?operation=searchRetrieve&collapsing=disabled&query=dc.relation%20all%20%22cb377013071%22](https://gallica.bnf.fr/services/engine/search/sru?operation=searchRetrieve&collapsing=disabled&query=dc.relation%20all%20%22cb377013071%22)
+[^LGE]: [https://www.collexpersee.eu/projet/disco-lge/](https://www.collexpersee.eu/projet/disco-lge/)
-The author would like to thank the CollEx-Persée group for supporting the
-DISCO-LGE project and is also grateful to the ASLAN project (ANR-10-LABX-0081)
-of the Université de Lyon, for its financial support within the French program
-"Investments for the Future" operated by the National Research Agency (ANR).
+The aim of the project was to digitise and make *La Grande Encyclopédie*
+available to the scientific community as well as the general public. A previous
+version of this encyclopedia was partially available on Gallica[^Gallica] but
+lacked in quality and its text had not been fully extracted from the pictures
+with an Optical Characters Recognition (OCR) system. This prevented an
+exhaustive study of the text with textometry tools such as TXM [@heiden2010]. As
+a prelude to project GEODE[^GEODE], the goal of CollEx-Persée was to produce a
+digital version of *La Grande Encyclopédie* with a quality comparable to the one
+of l'*Encyclopédie* provided by the ARTFL[^ARTFL] project in order to conduct
+a diachronic study of both encyclopedias.
+
+[^Gallica]: [https://gallica.bnf.fr/services/engine/search/sru?operation=searchRetrieve&collapsing=disabled&query=dc.relation%20all%20%22cb377013071%22](https://gallica.bnf.fr/services/engine/search/sru?operation=searchRetrieve&collapsing=disabled&query=dc.relation%20all%20%22cb377013071%22)
+[^GEODE]: [https://geode-project.github.io/](https://geode-project.github.io/)
+[^ARTFL]: [http://artfl-project.uchicago.edu/](http://artfl-project.uchicago.edu/)
## "Encyclopedia"
In common parlance, the terms "dictionaries" and "encyclopedias" are used as
near synonyms to refer to books compiling vast amounts of knowledge into lists
of definitions ordered alphabetically. Their similarity is even visible in the
-way they are coordinated in the full title of the *Encyclopédie ou Dictionnaire
-raisonné des sciences des arts et des métiers* published by Diderot and
-d'Alembert between 1751 and 1772 and which is probably the most famous work of
-the genre and a symbol of the Age of Enlightenment. If the word "encyclopedia"
-is nowadays part of our vocabulary, it was much more unusual and in fact
-controversial when Diderot and d'Alembert decided to use it in the title of
-their book.
+way they are coordinated in the full title of the *Encyclopédie* which is
+probably the most famous work of the genre and a symbol of the Age of
+Enlightenment. If the word "encyclopedia" is nowadays part of our vocabulary, it
+was much more unusual and in fact controversial when Diderot and d'Alembert
+decided to use it in the title of their book.
The definition given by Furetière in his *Dictionnaire Universel* in 1690 is
still close to its greek etymology: a "ring of all knowledges", from *κÏκλος*,
@@ -90,7 +94,7 @@ hubris: "C'est une témérité à un homme de vouloir posséder l'Encyclopédie"
("it is a recklessness for a man to want to possess Encyclopedia").
Beyond this moral reproach, the concept that pleased Rabelais was somewhat dated
-at the end of the 17\textsuperscript{th} century and attacked in the
+at the end of the 17^th^ century and attacked in the
*Dictionnaire Universel François et Latin*, commonly refered to as the
*Dictionnaire de Trevoux*, as utterly "burlesque" ("parodic"). The entry for
"Encyclopédie" remained unchanged in the four editons issued between 1721 and
@@ -110,27 +114,27 @@ against the philosophers of the Enlightenment.
The attacks do not remain ignored by Diderot who starts the very definition of
the word "Encyclopédie" in the *Encyclopédie* itself by a strong rebuttal. He
directly dismisses the concerns expressed in the *Dictionnaire de Trevoux* as
-mere self-doubt that their authors should not generalise to mankind, then leaves
-the main point to a latin quote by chancelor Bacon, who argues that a
-collaborative work can achieve much more than any talented man could: what could
-possibly not be within reach of a single man, within a single lifetime may be
-achieved by a common effort throughout generations (Lojkine, 2013).
+mere self-doubt that their authors should not generalise to anyone, then leaves
+the main point to a latin quote by chancelor Bacon [@lojkine2013], who argues
+that a collaborative work can achieve much more than any talented man could:
+what could possibly not be within reach of a single man, within a single
+lifetime may be achieved by a common effort throughout generations.
-History hints that Diderot's opponents took his defense of the feasability of
+History hints that Diderot's opponents took his defence of the feasability of
the project quite seriously, considering the fact that they got the
*Encyclopédie*'s privileges to be revoked again six years after its publication
-was resumed. As a consequence, the remaining ten volumes containing the text of
-the articles had to be published illegally until 1765, thanks to the secret
-protection of Malesherbes who — despite being head of royal censorship — saved
-the manuscripts from destruction. They were printed secretly outside of Paris
-and the books were (falsely) labeled as coming from Neufchâtel. Following the
-high demand from the booksellers who feared they would lose the money they had
-invested in the project, a special privilege was issued for the volumes
-containing the plates, which were released publicly from 1762 to 1772.
+was resumed [@moureau2001]. As a consequence, the remaining ten volumes
+containing the text of the articles had to be published illegally until 1765,
+thanks to the secret protection of Malesherbes who — despite being head of royal
+censorship — saved the manuscripts from destruction. They were printed secretly
+outside of Paris and the books were (falsely) labeled as coming from Neufchâtel.
+Following the high demand from the booksellers who feared they would lose the
+money they had invested in the project, a special privilege was issued for the
+volumes containing the plates, which were released publicly from 1762 to 1772.
In any case, in their last edition in 1771 the authors of the *Dictionnaire de
Trevoux* had no choice but to acknowledge the success of the encyclopedic
-projects of the 18\textsuperscript{th} century. In this version, the definition
+projects of the 18^th^ century. In this version, the definition
was entirely reworked, mildly stating that good encyclopedias are difficult to
make because of the amount of knowledge necessary and work needed to keep up
with scientific progress instead of calling the effort a parody. It credits
@@ -174,24 +178,46 @@ departing from them in terms of purpose.
# The *dictionaries* TEI module
+The XML-TEI standard has a modular structure consisting of optional parts each
+covering specific needs such as the physical features of a source document, the
+transcription of oral corpora or particular requirements for textual domains
+like poetry, or, in our case, dictionaries. After describing why the dedicated
+module was a natural candidate to meet our needs, we formalise tools from
+graph theory to browse the specifications of this standard in a rational way and
+explore this module in detail.
+
+## A good starting point
+
Data produced in the context of a project such as DISCO-LGE cannot be useful to
-future other scientific projects unless it is *interoperable* and *reusable*.
-These are the two last key aspects of the FAIR[^FAIR] principles (*findability*,
+future scientific projects unless it is *interoperable* and *reusable*. These
+are the two last key aspects of the FAIR[^FAIR] principles (*findability*,
*accessibility*, *interoperability* and *reusability*) which we strive to follow
as a guideline for efficient and quality research. It entails using standard
formats and a standard for encoding historical texts in the context of digital
humanities is XML-TEI, collectively developped by the *Text Encoding Initiative*
-consortium. It publishes a set of technical specifications under the form of
+consortium which publishes a set of technical specifications under the form of
XML schemas, along with a range of tools to handle them and training resources.
[^FAIR]: [https://www.go-fair.org/fair-principles/](https://www.go-fair.org/fair-principles/)
-The XML-TEI standard has a modular structure consisting of optional parts each
-covering specific needs such as the physical features of a source document, the
-transcription of oral corpora or particular requirements for textual domains
-like poetry, or, in our case, dictionaries.
+The *dictionaries* module has been leveraged to encode dictionaries in projects
+NENUFAR[^NENUFAR] and BASNUM[^BASNUM] to encode respectively the *Petit Larousse
+Illustré* published by Pierre Larousse in 1905 [@bohbot2018], roughly
+contemporary to our target encyclopedia and the *Dictionnaire Universel* by
+Furetière, or rather its second edition edited by Henri Basnage de Beauval, an
+encyclopedic dictionary from the very early 18^th^ century [@williams2017].
+These successes made it a good starting point for our own encoding but the
+former does not have the encyclopedic dimension our corpus has and the latter is
+a much older text which had a tremendous influence on the european encyclopedic
+effort of the 18^th^ century but is not as clearly separated from the
+dictionaric stem as *La Grande Encyclopédie* is. For these reasons, we could not
+directly reuse the encoding schemes used in these projects and had to explore
+the XML-TEI schema systematically to devise our own.
-In what follows, we need to name and manipulate XML elements. We choose to
+[^NENUFAR]: [https://cahier.hypotheses.org/nenufar](https://cahier.hypotheses.org/nenufar)
+[^BASNUM]: [https://anr.fr/Projet-ANR-18-CE38-0003](https://anr.fr/Projet-ANR-18-CE38-0003)
+
+In this chapter, we need to name and manipulate XML elements. We choose to
represent them in a monospace font, in the standard XML autoclosing form within
angle brackets and with a slash following the element name like `<div/>` for a
`div`[^div] element. We do not mean by this notation that they cannot contain
@@ -203,8 +229,6 @@ attributes.
[^div]: [https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-div.html](https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-div.html)
-## Content
-
## A graph problem
The XML-TEI specification contains 590 elements, which are each documented on
@@ -216,19 +240,21 @@ combinations sharply increases with each step.
We transform the problem by representing this network as a directed graph, using
elements of XML-TEI as nodes and placing edges if the destination node may be
contained within the source node according to the schema. Please note that the
-"element" word is here used with the same meaning as in the TEI documentation to
+word "element" is here used with the same meaning as in the TEI documentation to
refer to the conceptual device characterised by a given tag name such as `p` or
`div` and not to a particular instance of them that may occur in a given
-document.
+document. Figure @fig:dictionaries-subgraph, by using this transformation to
+display the *dictionaries* module, hints at the overall complexity of the whole
+specification.
-
+{#fig:dictionaries-subgraph}
-### Definitions
+### Definitions {-}
By iterating several times the operation of moving on that graph along one edge,
that is, by considering the transitive closure of the relation "be connected by
an edge" we define *inclusion paths* which allow us to explore which elements
-may be nested under one another.
+may be nested under which other.
The nodes visited along the way represent the intermediate XML elements to
construct a valid XML tree according to the TEI schema. Given the top-down
@@ -244,18 +270,18 @@ usually called a cycle and we may be tempted in our context to refine this and
name them *inclusion cycles*. The `<address/>` element provides us with an
example for this configuration: although an `<address/>` element may not
directly contain another one, it may contain a `<geogName/>` which, in turn, may
-contain a new `<address/>` element. From a graph theory perspective, we can say
+contain a new `<address/>` element. From a graph theory perspective, we can say
that it admits an inclusion cycle of length two.
-### Applications
+### Applications {-}
-Using classical, well-known methods such as Dijkstra's algorithm (Dijkstra, 1959)
+Using classical, well-known methods such as Dijkstra's algorithm [@dijkstra59]
allows us to explore the shortest inclusion paths that exist between elements.
Though a particular caution should be applied because there is no guarantee that
the shortest path is meaningful in general, it at least provides us with an
efficient way to check whether a given element may or not be nested at all under
-another one and gives an order of magnitude on the length of the path to expect.
-Of course the accuracy of this heuristic decreases as the length of the elements
+another one and gives a lower bound on the length of the path to expect. Of
+course the accuracy of this heuristic decreases as the length of the elements
increases in the perfect graph representing the intended, meaningful path
between two nodes that a human specialist of the TEI framework could build.
@@ -289,7 +315,9 @@ length 3 returns as expected the path through `<entry/>`, among others. Overall,
we get a good general idea: `<pos/>` does not need to be nested very deep, it
can appear quite near the "surface" of article entries.
-### The `<entry/>` element
+## Content of the module
+
+### The `<entry/>` element {-}
The central element of the *dictionaries* module is the `<entry/>` element meant
to encode one single entry in a dictionary, that is to say a head word
@@ -309,35 +337,32 @@ as the natural top-most element for an article. This somewhat contrived example
hopes to further demonstrate the application of a graph-centred approach to
understand the inner workings of the XML-TEI schema.
-### Information about the headword itself
+### Information about the headword itself {-}
Once a block for an article is created, it may contain elements useful to
-represent features such as
-
-- its written and spoken forms: `<form/>`
-- a group of grammatical information: `<gramGrp/>`, that may itself contain as
- previously demonstrated `<case/>`, `<gen/>`, `<number/>` or `<pers/>` to
- describe the form itself for instance, but also information about the
- categories it belongs to like `<iType/>` for its inflection class in languages
- with a declension system or `<pos/>` for its part-of-speech
-- its etymology: `<etym/>`
-- its variants if there is a different spelling in a variety of the language or
- if it has changed through time: `<usg/>` (though it is not its only purpose)
-
-All these are examples and by no means an exhaustive list; the complete set
-provides the encoder with a toolbox to describe all the information related to
-the form the entry is found at and seems general enough to accomodate the
-structure of any book indexing entries by words.
-
-### Cross-references
+represent various of its features. Its written and spoken forms are usually
+encoded by `<form/>` elements. Grammatical information like the `<case/>`,
+`<gen/>` or `<number/>` and `<pers/>` can be contained within a `<gramGrp/>`,
+along with information about the categories it belongs to like `<iType/>` for
+its inflection class in languages with a declension system or `<pos/>` for its
+part-of-speech. The `<etym/>` element is made to hold the etymology of an entry.
+In the case when there are alternative spellings in varieties of the language or
+if the spelling has changed over time, `<usg/>` can be used.
+
+All these examples are by no means an exhaustive list; the complete set provides
+the encoder with a toolbox to describe all the information related to the form
+the entry is found at and seems general enough to accomodate the structure of
+any book indexing entries by words.
+
+### Cross-references {-}
A common feature shared by dictionaries and encyclopedias is the ability to
connect entries together by using a word or short phrase as the link, referring
the reader to the related concept. This is known as cross-references and can
appear either when the definition of a term is adjacent to another one or to
-catch alternative spellings where some readers might expect the word to appear
-and redirect them to the form chosen as the reference. In XML-TEI, this is done
-with the `<xr/>` element. It usually contains the whole phrase performing the
+catch alternative spellings where some readers might expect to find the word and
+redirect them to the form chosen as the reference. In XML-TEI, this is done with
+the `<xr/>` element. It usually contains the whole phrase performing the
redirection, with an imperative locution like "please see […]".
The "active" part of the cross-reference, that is the very word within the
@@ -348,7 +373,7 @@ in this description of the toolbox because it is particularly useful in the
context of dictionaries. This element may have a target attribute which points
to the other resource to be accessed by the interested reader.
-### Content
+### Definitions {-}
The remaining part of entries is also usually the largest and represents the
content associated to the headword by the entry. In a dictionary, that is its
@@ -360,7 +385,7 @@ of this versatile element) and other high-level information such as translations
in other languages. Both `<def/>` and `<usg/>` elements may appear directly
under the `<entry/>`.
-### Structural remarks
+### Structural remarks {-}
Before concluding this description of the *dictionaries* module from the
perspective of someone trying to concretely encode a particular dictionary or
@@ -400,7 +425,7 @@ several possible readings of an unclear group of words in a manuscript, or when
the encoder is trying to compile a single version of a piece of work from
several sources which disagree over some passage. In both case, it appears
obvious that it is not something that is expected to occur naturally in the
-course of an article in the general case.
+course of an article in general.
Thus, despite a rather dense internal connectivity, the *dictionaries* module
fails to provide encoders with a device to represent recursively nesting
@@ -413,7 +438,9 @@ articles in particular, we identify structures which are specific to
encyclopedias and not compatible with the *dictionaries* module presented above.
We hence conclude that this module is not able to encode arbitrary encyclopedic
content and propose a new fully TEI-compliant encoding scheme remaining outside
-of it.
+of it. We proceed with remarks about the needs of automated encoding processes
+and compare our proposal with other strategies to overcome the issues previously
+identified with the dedicated module for dictionaries.
## Idiosynchrasies of encyclopedias
@@ -422,7 +449,7 @@ noticeable differences. It is difficult to make a precise list because the
editorial choices may vary greatly between encyclopedias but we discuss some of
the most obvious.
-### Organised knowledge
+### Organised knowledge {-}
The first immediately visible feature that sets encyclopedias apart from
dictionaries and can be found in the *Encyclopédie* as well as in *La Grande
@@ -445,12 +472,13 @@ between several entries sharing the same headword, the concept itself has
evolved beyond this mere distinction. Looking back at the *Encyclopédie*, the
adjective *raisonné* in the rest of the title directly introduces a notion of
structure that links back to the "Systême figuré des connoissances humaines"
-(Blanchard et al., 2002). The authors have devised a branching system to
-classify all knowledge, and the occurrence at the beginning of articles, more
-than a tool to clear up possible ambiguities also points the reader to the
-correct place in this mind map.
+[@blanchard2002] which schematic structure is shown in Figure
+@fig:systeme-figure. The authors have devised a branching system to classify all
+knowledge, and the occurrence at the beginning of articles, more than a tool to
+clear up possible ambiguities also points the reader to the correct place in
+this mind map.
-{width=200px}
+{width=300px #fig:systeme-figure}
The situation regarding subject indicators is hardly better outside of the
module. The `<domain/>` element despite its name belongs exclusively in the
@@ -468,29 +496,29 @@ This point, although not the most concerning, still remains the hardest to
address but all things considered the `<usg/>` element stands out as the most
relevant.
-### The notion of meaning
+### The notion of meaning {-}
Notwithstanding the correct way to represent domains of knowledge, their extent
itself raises concerns regarding the *dictionaries* module. Indeed, among the
-vast collection of domains covered are sometimes historical articles and
-biographies. If the notion of meaning can appear ill-fitting for a text
-describing a series of historical events, one may still argue that it groups
-them into a concept and associates it to the name of the event. But when it
-comes to relating the life of a person, describing their relation to events and
-other persons comes out even further from the notion of meaning. To what extent
-is it relevant to consider that having discovered such or such thing or to have
-been born on a certain time at a certain place *defines* someone ?
-
-
-
-Moreover, encyclopedias, inheriting as much as they have from the philosophical
-Enlightenment, are not only spaces designed to assert, they also intrinsically
-include an interrogative component. Some articles lay down the basis required to
-understand the complexity of an issue and invite the reader to consider it
-without providing a definite answer, going as far as to explicitly using
-question marks.
-
-
+vast collection of domains covered in encyclopedias in general and in *La Grande
+Encyclopédie* in particular are historical articles and biographies. If the
+notion of meaning can appear at least ill-fitting for a text describing a series
+of historical events, one may still argue that it groups them into a concept and
+associates it to the name of the event. But when it comes to relating the life
+of a person, describing their relation to events and other persons comes out
+even further from the notion of meaning. Entries such as the one about SANJO
+Sanetomi (see Figure @fig:sanjo) do not constitute a *definition*.
+
+{#fig:sanjo}
+
+Moreover, encyclopedias, because of all that they have inherited from the
+philosophical Enlightenment, are not only spaces designed to assert, they also
+intrinsically include an interrogative component. Some articles lay down the
+basis required to understand the complexity of an issue and invite the reader to
+consider it without providing a definitive answer, going as far as to explicitly
+use question marks as in the article "Action" displayed in Figure @fig:action.
+
+{#fig:action}
In this extract, the author devises a hypothetical situation to illustrate how
difficult it is to draw the line between two supposedly mutually exclusive
@@ -501,7 +529,7 @@ idea that the term eludes definition, wrapping it in a `<sense/>`, or worse, a
As a result, the use of `<sense/>` and `<def/>` is not appropriate for
encyclopedic content in general.
-### Nested structures
+### Nested structures {-}
The final difficulty can be considered as a partial consequence of the previous
one on the structure of articles. The difficulty to define complex concepts is
@@ -509,20 +537,20 @@ the very reason why authors approach their subjects from various angles,
circumnavigating it as a best approximation. This strategy favours long,
structured developments with sections and subsections covering the multiple
aspects of the topic: from a historical, political, scientific point of view…
-The longest articles can thus span several dozens of pages. They can contain
-substructures with titles on at least three levels (for instance, a `a)` under a
-`1)` under a `I.`), each of which are in turn generally developed over several
-paragraphs.
+The longest articles, such as article "Europe" shown in Figure @fig:europe, can
+thus span several dozens of pages. They can contain substructures with titles on
+at least three levels (for instance, a `a)` under a `1)` under a `I.`), each of
+which are in turn generally developed over several paragraphs.
-
+{#fig:europe}
The nested structure that we have just evidenced demands of course a nesting
structure to accomodate it. More precisely it guides our search of XML elements
by giving us several constraints: we are looking for a pair of elements, the
first representing a (sub)section must be able to include both itself and the
-second element, which does not have any special constraint in addition to the one
-it shares with the first, which is to have a semantics compatible with our
-purpose. In addition, the first element must be able to contain several `<p/>`
+second element, which does not have any special constraint except the one to
+have a semantics compatible with our purpose of using it to represent section
+titles. In addition, the first element must be able to contain several `<p/>`
elements, `<p/>` being the reference element to encode paragraphs according to
the XML-TEI documentation.
@@ -533,7 +561,7 @@ and `<title/>` — the latter with the possibility to set its `type` attribute t
`sub` — stand out as the best candidates for the semantics condition on the
second element.
-#### Candidates in the *dictionaries* module
+#### Candidates in the *dictionaries* module {-}
Filtering the content of the module to keep only the elements which can at the
same time contain themselves, be included under `<entry/>` and include a `<p/>`
@@ -559,40 +587,43 @@ occur in the middle of each one of the inclusion paths that define the structure
required to encode encyclopedic discourse, we find 21 elements but none of them
stand out as an obvious good solution: all paths to include the `<p/>` element
from any *dictionaries* element either contains a `<figure/>` (which we have
-previously encountered earlier when we were practising our graph approach to
-search for inclusions between `<entry/>` and `<entryFree/>` and dismissed as not
-useful in general), a `<stage/>` (reserved to stage direction in dramatic works)
-or a `<state/>` (used to describe a temporary quality in a person or place),
-again not even close to what we want. The paths to either `<head/>` or
-`<title/>` are similarly disappointing. Again, changing `<entry/>` for
-`<entryFree/>` returns the exact same candidates. If that is not a thorough
-proof that none of these elements could fulfill our purpose, it is a fact than
-no element in this module appears as an obvious good solution and a serious hint
-to keep looking somewhere else.
-
-#### Widening the search
+encountered earlier when we were practising our graph approach to search for
+inclusions between `<entry/>` and `<entryFree/>` and dismissed as not useful in
+general), a `<stage/>` (reserved to stage direction in dramatic works) or a
+`<state/>` (used to describe a temporary quality in a person or place), again
+not even close to what we want. The paths to either `<head/>` or `<title/>` are
+similarly disappointing. Again, changing `<entry/>` for `<entryFree/>` returns
+the exact same candidates. If that is not a thorough proof that none of these
+elements could fulfill our purpose, it is a fact than no element in this module
+appears as an obvious good solution and a serious hint to keep looking somewhere
+else.
+
+#### Widening the search {-}
We hence widen our search to include elements outside the *dictionaries* module
which could be used to encode our sections and subsections, under the same
constraint as before to try and find a composite solution that would remain
under the `<entry/>` element even if resorting to subcomponents outside of the
-dedicated module. Only three elements are returned:
-
-- `<figure/>`: not any more useful to represent the content of encyclopedic
- discourse than as a helper to include paragraphs
-- `<metamark/>`: a very useful device to transcribe the edition marks than may
- appear on a particular primary source to alter the normal flow of the text and
- suggest an alternative reading (deletion, insertion, reordering, this is about
- a human editing the text from a given physical copy of it), again really of no
- use for a part of an article describing the geology of Europe for instance.
-- `<note/>`: the first element that might at least resemble what we are looking
- for. It is meant to contain text, is about explaning something and seems
- general enough (not specific to a given genre, or to the occurrence of a
- particular object on the page). Unfortunately, its semantics still seems a bit
- off compared to our need. The documentation describes it as an "additional
- comment", and, moreover "out of the main textual stream" whereas the long
- developments in article are the very matter that inhabits the columns of text
- encyclopedias are made of.
+dedicated module. Only three elements are returned: `<figure/>`, `<metamark/>`
+and `<note/>`.
+
+The first one as we have repeatedly underlined is meant for graphic information
+and is not suitable for text content in general.
+
+The purpose of `<metamark/>` is to transcribe the edition marks than may appear
+on a particular primary source in order to alter the normal flow of the text and
+suggest an alternative reading (deletion, insertion, reordering, this is about a
+human editing the text from a given physical copy of it), but it is
+unfortunately of no use to encode a section of an article.
+
+The first element that might at least resemble what we are looking for is the
+last one, `<note/>`. It is meant to contain text, is about explaning something
+and seems general enough (not specific to a given genre, or to the occurrence of
+a particular object on the page). Unfortunately, its semantics still seems a bit
+off compared to our need. The documentation describes it as an "additional
+comment" which appears "out of the main textual stream" whereas the long
+developments in articles are the very matter of the text of encyclopedias, not
+mere remarks in the margins or at the foot of pages.
## Encoding within the *core* module
@@ -612,30 +643,32 @@ what happens at the level of each article, right under the `<body/>` element.
Everything related to metadata happens as expected in the file's `<teiHeader/>`
which is well-enough equiped to handle them. In order to present our scheme
throughout the following section we will be progressively encoding a reference
-article, "Cathète" from tome 9.
+article, "Cathète" from tome 9 reproduced in Figure @fig:cathete-photo.
-
+{#fig:cathete-photo}
-### The scheme
+### The scheme {-}
Remaining within the *core* module for the structure, almost all useful elements
are available and our encoding scheme merely quotes the official documentation.
Each article is represented by a `<div/>`. We suggest setting an `xml:id`
-attribute on it with as value the — unique in the whole corpus, or made so by
-suffixing a number representing its rank among the various occurrences, even
-when there's only one for the sake of regularity — head word of the entry,
-normalised to lowercase, stripping spaces and replacing all non-alphanumerical
-characters by a dash `'-'` to avoid issues with the XML encoding.
+attribute on it with the head word of the entry — unique in the whole corpus, or
+made so by suffixing a number representing its rank among the various
+occurrences, even when there's only one for the sake of regularity — as its
+value, normalised to lowercase, stripping spaces and replacing all
+non-alphanumerical characters by a dash (`'-'`) to avoid issues with the XML
+encoding. Figure @fig:cathete-xml-0 illustrates this choice for the container
+element on the article "Cathète" previously displayed.
-
+{#fig:cathete-xml-0}
Inside this element should be a `<head/>` enclosing the headword of the article.
The usual sub-`<hi/>` elements are available within `<head/>` if the headword is
highlighted by any special typographic means such as bold, small capitals, etc.
-The one disappointment of the encoding scheme we are currently defining is the
-lack of support for a proper way to encode subject indicators.
+The one disappointment of the encoding scheme we are defining in this chapter is
+the lack of support for a proper way to encode subject indicators.
-The best candidate we have found so far was `<ùsg/>` from the *dictionaries*
+The best candidate we have found so far was `<usg/>` from the *dictionaries*
module but it is not available directly under a `<head/>` element. All inclusion
paths from the latter to the former of length less than or equal to 3 contain
irrelevant elements (`<cit/>`, `<figure/>`, `<castList/>` and `<nym/>`) so it
@@ -643,66 +676,69 @@ must be discarded. The next best elements appear to be `<term/>` (not very
accurate) and `<rs/>` ("referring string", quite a general semantics but a
possible match — subject indicators refer to a given domain of knowledge —
although all the examples in the documentation refer to concrete persons,
-places or object, not to the abstract objects that mathematics or poetry can be)
+places or object, not to the abstract objects that mathematics or poetry are).
For this reason, we do not recommend any special encoding of the subject
indicator but leave it open to each particular context: they are often
abbreviated so an `<abbr/>` may apply, in *La Grande Encyclopédie*, biographies
are not labeled by a knowledge domain but usually include the first name of the
person when it is known so in that case an element like `<persName/>` is still
-appropriate.
+appropriate. This choice applied to the same article "Cathète" produces Figure
+@fig:cathete-xml-1.
-
+{#fig:cathete-xml-1}
We then propose to wrap each different meaning in a separate `<div/>` with the
`type` attribute set to `sense` to refer to the `<sense/>` element that would
-have been used within the *core* module. Each sense should be numbered with the
-`n` attribute.
+have been used within the *core* module. The `<div/>`s should be numbered
+according to the order they appear in with the `n` attribute starting from `0`
+as shown in Figure @fig:cathete-xml-2.
-
+{#fig:cathete-xml-2}
In addition, each line within the article must start with a `<lb/>` to mark its
-beginning including before the `<head/>` element, which, although a surprising
-setup, underlines the fact that in the dense layout of encyclopedias, the
-carriage return separating two articles is meaningful. Stating each new line
-explicitly keeps enough information to reconstruct a faithful facsimile but it
-also has the advantage of highlighting the fact than even though the definition
-is cut from the headword by being in a separate XML element, they still occur on
-the same line, which is a typographic choice usually made both in encyclopedias
-and dictionaries where space is at a premium.
+beginning including before the `<head/>` element as demonstrated by Figure
+@fig:cathete-xml-3, which, although a surprising setup, underlines the fact that
+in the dense layout of encyclopedias, the carriage return separating two
+articles is meaningful. Stating each new line explicitly keeps enough
+information to reconstruct a faithful facsimile but it also has the advantage of
+highlighting the fact than even though the definition is cut from the headword
+by being in a separate XML element, they still occur on the same line, which is
+a typographic choice usually made both in encyclopedias and dictionaries where
+space is at a premium. .
To complete the structure, the various sections and subsections occurring
within the article body may be nested as usual with `<div/>` and sub-`<div/>`s,
filled with `<p/>` for paragraphs which can each be titled with `<head/>`
elements local to each `<div/>`.
-
+{#fig:cathete-xml-3}
-Some articles have figures with captions, which should be encoded the standard
-way by `<figure/>` and `<figDesc/>`.
+Some articles such as "Boumerang" have figures with captions, as illustrated by
+Figure @fig:boumerang-photo, which should be encoded the standard way by
+`<figure/>` and `<figDesc/>` as in Figure @fig:boumerang-xml.
-{height=300px}
+{height=300px #fig:boumerang-photo}
-
+{#fig:boumerang-xml}
-Another issue of giving up on `<entry/>` is the unavailability of the `<xr/>`
-element to represent cross-references which occur in encyclopedias as well as in
-dictionaries. We prefer giving up on it to keep only the `<ref/>` element which
-is available in the context of a `<p/>`. Its `target` attribute should be set to
-the `xml:id` of the article it points to, prefixed with a `'#'` but without any
-other file or url prepended, if it can be determined accurately (a unique
-article with the corresponding article, or ambiguity solved with the help of the
-domain annotations). Another solution would have been to introduce a
-`<dictScrap/>` element for the sole purpose of placing an `<xr/>` but we
-advocate against it on account of the verbosity it would add to the encoding and
-the fact that it implicitly suggests that the previous context was not the one
-of a dictionary.
+Another issue arising from giving up on `<entry/>` is the unavailability of the
+`<xr/>` element, not allowed under any of the *core* elements we use but which
+is useful to represent cross-references occurring in encyclopedias as well as in
+dictionaries, for example in article "Gelocus" (see Figure @fig:gelocus-photo).
+We prefer to use the `<ref/>` element instead which is available in the context
+of a `<p/>`. Its `target` attribute should be set to the `xml:id` of the
+article it points to, prefixed with a `'#'` as shown in Figure @fig:gelocus-xml.
+Another solution would have been to introduce a `<dictScrap/>` element for the
+sole purpose of placing an `<xr/>` but we advocate against it on account of the
+verbosity it would add to the encoding and the fact that it implicitly suggests
+that the previous context was not the one of a dictionary.
-
+{#fig:gelocus-photo}
-
+{#fig:gelocus-xml}
-But a typical page of an encyclopedia also features peritext elements, giving
+A typical page of an encyclopedia also features peritext elements, giving
information to the reader about the current page number along with the headwords
of the first and last articles appearing on the page. Those can be encoded by
`<fw/>` elements ("forme work") which `place` and `type` attributes should be
@@ -711,27 +747,31 @@ recognised (those short elements on the border of pages are the ones typically
prone to suffer damages or be misread by the OCR).
Finally there are other TEI elements useful to represent "events" in the flow of
-the text, like the beginning of a new column of text or of a new page. The usual
-appropriate elements (`<pb/>` for page beginning, `<cb/>` for column beginning)
-may and should be used with our encoding scheme.
+the text, like the beginning of a new column of text or of a new page. Figure
+@fig:alcala-photo shows the top left of the last page of the first tome of *La
+Grande Encyclopédie* which features peritext elements while marking the
+beginning of a new page. The usual appropriate elements (`<pb/>` for page
+beginning, `<cb/>` for column beginning) may and should be used with our
+encoding scheme as demonstrated by Figure @fig:alcala-xml.
-{width=350px}
+{width=350px #fig:alcala-photo}
-
+{#fig:alcala-xml}
-### Currently implemented
+### Currently implemented {-}
The reference implementation for this encoding scheme is the program
soprano[^soprano] developed within the scope of project DISCO-LGE to
automatically identify individual articles in the flow of raw text from the
columns and to encode them into XML-TEI files. Though this software has already
-been used to produce the first TEI version of *La Grande Encyclopédie*, it
-does not yet follow the above specification perfectly. Here is for instance the
-encoded version of article "Cathète" it currently produces:
+been used to produce the first TEI version of *La Grande Encyclopédie*, it does
+not yet follow the above specification perfectly. Figure
+@fig:cathete-xml-current shows the encoded version of article "Cathète" it
+currently produces:
[^soprano]: [https://gitlab.huma-num.fr/disco-lge/soprano](https://gitlab.huma-num.fr/disco-lge/soprano)
-
+{#fig:cathete-xml-current}
The headword detection system is not able to capture the subject indicators yet
so it appears outside of the `<head/>` element. No work is performed either to
@@ -762,15 +802,14 @@ by `soprano` when inferring the reading order before segmenting the articles.
Encyclopedias are particularly long books, spanning numerous tomes and
containing several tenths of thousands of articles. The *Encyclopédie* comprises
over 74k articles and *La Grande Encyclopédie* certainly more than 100k (the latest
-version produced by `soprano` produced 160k articles, but their segmentation is
+version produced by `soprano` created 160k articles, but their segmentation is
still not perfect and if some article beginning remain undetected, all the very
long and deeply-structured articles are unduly split into many parts, resulting
-globally in an overestimation of the total number). In any case, it consists of
-31 tomes of 1200 pages each.
+globally in an overestimation of the total number).
XML-TEI is a very broad tool useful for very different applications. Some
elements like `<unclear/>` or `<factuality/>` can encode subtle semantics
-information (for the second case, adjacent to a notion as elusive as truth)
+information (for the second one, adjacent to a notion as elusive as truth)
which requires a very deep understanding of a text in its entirety and about
which even some human experts may disagree.
@@ -792,7 +831,8 @@ Encyclopédie*, virtually all the redirections (that is, to the extent of our
knowledge, absolutely all of them though of course some special case may exist,
but they are statistically rare enough that we have not found any yet) appear
within parenthesis, and start with the verb "voir" abbreviated as a single,
-capital "V." as illustrated above in the article "Gelocus".
+capital "V." as illustrated above in the article "Gelocus" (see again Figure
+@fig:gelocus-photo).
Although this has not been implemented yet either, we hope to be able to detect
and exploit those patterns to correctly encode cross-references. Getting the
@@ -812,20 +852,20 @@ instance the empty elements already discussed above. For articles, it pushes
lines onto a stack and flushes it each time it encounters the beginning of the
following article. This allows the amount of memory required to remain
reasonable and even lets them be parallelised on most modern machines. Thus,
-even taking over three minutes per tome, the total processing time can be lowered to
-around forty minutes for the whole of *La Grande Encyclopédie* instead of over one hour
-and a half.
+even taking over three minutes per tome, the total processing time can be
+lowered to around forty minutes on a machine with 16Go of RAM for the whole of
+*La Grande Encyclopédie* instead of over one hour and a half.
## Comparison to other approaches
-The above section about the structure of the *dictionaries* module and the
+The previous section about the structure of the *dictionaries* module and the
features found in encyclopedias follows quite closely our own journey trying to
encode first manually then by automatic means the articles of our corpus. This
back and forth between trying to find patterns in the graph which reflects the patterns
found in the text and questioning the relevance of the results explains the
choice we ended up making but also the alternatives we have considered.
-### Bend the semantics
+### Bend the semantics {-}
Several times, the issue of the semantics of some elements which posess the
properties we need came up. This is the case for instance of the `<sense/>` and
@@ -834,17 +874,14 @@ consider that their inclusion properties is part of what defines them, and hence
justifies their ways in creative ways not directly recommended by the TEI
specifications.
-This is the approach followed by project BASNUM[^BASNUM] which studies and
-provides a XML-TEI encoding of the *Dictionnaire Universel* by Furetière, or
-rather its second edition edited by Basnage, an encyclopedic dictionary from the
-very early 18\textsuperscript{th} century. In the articles encoded for this
-project, `<note/>` elements are nested and used to structure the encyclopedic
-developments that occur in the articles.
+This is the approach followed by project BASNUM[^BASNUM]. In the articles
+encoded for this project, `<note/>` elements are nested and used to structure
+the encyclopedic developments that occur in the articles.
We have chosen not to follow the same path in the name of the FAIR principles to
avoid the emergence of a custom usage differing from the documented one.
-### Custom schema
+### Custom schema {-}
The other major reason behind our choice was the inclusion rules which exist
between TEI elements and pushed us to look for different combinations. Another
@@ -853,8 +890,8 @@ graph itself, that is to say modify the rules. If `<entry/>` is the perfect
element to encode article themselves, all that is really missing is the ability
to accomodate nested structures with the `<div/>` element. This would also have
the advantage of recovering the `<usg/>` and `<xr/>` elements which we have
-recognized as useful and which we lose as part of the tradeoff to get nested
-sections. Generating customized TEI schemas is made really easy with tools like
+recognised as useful and which we lose as part of the tradeoff to get nested
+sections. Generating customised TEI schemas is made really easy with tools like
ROMA[^ROMA], which we used to preview our change and suggest it to the TEI
community.
@@ -889,13 +926,13 @@ XML-TEI while being able to represent the content of encyclopedias in all their
complexity. A first implementation of this encoding, incomplete as it may be,
demonstrates its practical usefulness.
+# Acknowledgement {-}
+
+The author would like to thank the CollEx-Persée group for supporting the
+DISCO-LGE project and is also grateful to the ASLAN project (ANR-10-LABX-0081)
+of the Université de Lyon, for its financial support within the French program
+"Investments for the Future" operated by the National Research Agency (ANR).
+
# Bibliography {-}
-- Bohbot, H., Frontini, F., Luxardo, G., Khemakhem, M. & Romary, L. (2018). Presenting the Nénufar Project: a Diachronic Digital Edition of the Petit Larousse Illustré. *GLOBALEX2018 - Globalex workshop at LREC2018, May 2018, Miyazaki, Japan.*
-- Jacquet-Pfau, C. (2015). Élaboration et destinée d’une encyclopédie à la fin du XIXe siècle: les trente-et-un volumes de La Grande Encyclopédie. Inventaire raisonné des sciences, des lettres et des arts par une Société de savants et de gens de lettres (1885-1902). In *Éla, Études de linguistique appliquée 177* (pp. 85-100).
-- Roe, G., Gladstone, C. & Morrissey, R. (2016). Discourses and Disciplines in the Enlightenment: Topic Modeling the French Encyclopédie. In *Frontiers in Digital Humanities 2*
-- Vigier, D., Moncla, L., Joliveau, T., Mcdonough K. & Brenon. A. (2019). GeoDISCO: Encyclopedic Geographical Discourse in France from the Enlightenment to Wikipedia. In *GIR'19, 13th International Workshop on Geographic Information Retrieval*, Nov 2019, Lyon, France.
-- Williams, G. (2017). Mapping a dictionary: Using Atlas ti and XML to analyse a late XVIIth century dictionary. In *RiCOGNIZIONI. Rivista di Lingue e Letterature straniere e Culture moderne, [S.l.], v. 4, n. 7* (pp. 161-180), june 2017. ISSN 2384-8987. [http://www.ojs.unito.it/index.php/ricognizioni/article/download/2104/2024](http://www.ojs.unito.it/index.php/ricognizioni/article/download/2104/2024)
-- Blanchard, G. & Olsen, M. (2002). Le système de renvoi dans l’Encyclopédie: Une cartographie des structures de connaissances au XVIIIe siècle. In *Recherches sur Diderot et sur l’Encyclopédie.* [http://journals.openedition.org/rde/122](http://journals.openedition.org/rde/122)
-- Lojkine, S. (2013). « Et l'auteur anonyme n'est pas un lâche… » Diderot, l'engagement sans le nom. In *Littératures classiques, 80*, (pp. 249-263). [https://doi.org/10.3917/licla.080.0249](https://doi.org/10.3917/licla.080.0249)
-- Moureau, F. (2001). *Le Roman vrai de l’Encyclopédie*. Paris, Gallimard. (pp. 124-129).
+\bibliography{biblio}
diff --git a/Makefile b/Makefile
index 2bccf40842de354a998bf3567722317be89d24bb..69e1ad0a17859d1ddf174f540d11159fc92de9fc 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,8 @@
FIGURES = action_t1 arbre boumerang_t7 cathète_t9 dictionaries europe_t16 gelocus_t18 last_page_top_left_t1 sanjo_t29
SNIPPETS = $(wildcard snippets/*.md)
+FILTERS = pandoc-fignos
FILE_NAME = ICHLL_Brenon
-DEPEDENCIES = $(FIGURES:%=ressources/%.png) $(SNIPPETS:%.md=%.png)
+DEPEDENCIES = $(FIGURES:%=ressources/%.png) $(SNIPPETS:%.md=%.png) biblio.bib
all: $(FILE_NAME).pdf
@@ -9,7 +10,7 @@ ICHLL_Brenon.pdf: $(DEPEDENCIES)
ICHLL_Brenon.docx: $(DEPEDENCIES)
%.pdf: %.md
- LANG=fr_FR.UTF-8 pandoc $< -o $@
+ LANG=fr_FR.UTF-8 pandoc $< $(FILTERS:%=--filter %) --bibliography=biblio.bib --csl=apa.csl --citeproc -o $@
%.png: %.pdf
pdftocairo -png -singlefile -r 400 $^ $(basename $@)
@@ -18,5 +19,5 @@ ICHLL_Brenon.docx: $(DEPEDENCIES)
dot -Tpng $< -o $@
%.docx: %.md
- LANG=fr_FR.UTF-8 pandoc $< --to docx --number-sections -o $@
+ LANG=fr_FR.UTF-8 pandoc $< --to docx --number-sections $(FILTERS:%=--filter %) --bibliography=biblio.bib --csl=apa.csl --citeproc -o $@
diff --git a/apa.csl b/apa.csl
new file mode 100644
index 0000000000000000000000000000000000000000..88342c85724594fd11cc3c080f062bd7cffa3039
--- /dev/null
+++ b/apa.csl
@@ -0,0 +1,1900 @@
+<?xml version="1.0" encoding="utf-8"?>
+<style xmlns="http://purl.org/net/xbiblio/csl" class="in-text" version="1.0" demote-non-dropping-particle="never" page-range-format="expanded">
+ <info>
+ <title>American Psychological Association 7th edition</title>
+ <title-short>APA</title-short>
+ <id>http://www.zotero.org/styles/apa</id>
+ <link href="http://www.zotero.org/styles/apa" rel="self"/>
+ <link href="http://www.zotero.org/styles/apa-6th-edition" rel="template"/>
+ <link href="https://apastyle.apa.org/style-grammar-guidelines/references/examples" rel="documentation"/>
+ <author>
+ <name>Brenton M. Wiernik</name>
+ <email>zotero@wiernik.org</email>
+ </author>
+ <category citation-format="author-date"/>
+ <category field="psychology"/>
+ <category field="generic-base"/>
+ <updated>2022-01-31T14:43:56+00:00</updated>
+ <rights license="http://creativecommons.org/licenses/by-sa/3.0/">This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 License</rights>
+ </info>
+ <locale xml:lang="en">
+ <terms>
+ <term name="editortranslator" form="short">
+ <single>ed. & trans.</single>
+ <multiple>eds. & trans.</multiple>
+ </term>
+ <term name="translator" form="short">trans.</term>
+ <term name="interviewer" form="short">
+ <single>interviewer</single>
+ <multiple>interviewers</multiple>
+ </term>
+ <term name="collection-editor" form="short">
+ <single>ed.</single>
+ <multiple>eds.</multiple>
+ </term>
+ <term name="circa" form="short">ca.</term>
+ <term name="bc"> B.C.E.</term>
+ <term name="ad"> C.E.</term>
+ <term name="letter">personal communication</term>
+ <term name="letter" form="short">letter</term>
+ <term name="issue" form="long">
+ <single>issue</single>
+ <multiple>issues</multiple>
+ </term>
+ </terms>
+ </locale>
+ <locale xml:lang="af">
+ <terms>
+ <term name="letter">persoonlike kommunikasie</term>
+ <term name="letter" form="short">brief</term>
+ </terms>
+ </locale>
+ <locale xml:lang="ar">
+ <terms>
+ <term name="letter">اتصال شخصي</term>
+ <term name="letter" form="short">خطاب</term>
+ </terms>
+ </locale>
+ <locale xml:lang="bg">
+ <terms>
+ <term name="letter">лична комуникациÑ</term>
+ <term name="letter" form="short">пиÑмо</term>
+ </terms>
+ </locale>
+ <locale xml:lang="ca">
+ <terms>
+ <term name="letter">comunicació personal</term>
+ <term name="letter" form="short">carta</term>
+ </terms>
+ </locale>
+ <locale xml:lang="cs">
+ <terms>
+ <term name="letter">osobnà komunikace</term>
+ <term name="letter" form="short">dopis</term>
+ </terms>
+ </locale>
+ <locale xml:lang="cy">
+ <terms>
+ <term name="letter">cyfathrebu personol</term>
+ <term name="letter" form="short">llythyr</term>
+ </terms>
+ </locale>
+ <locale xml:lang="da">
+ <terms>
+ <term name="et-al">et al.</term>
+ <term name="letter">personlig kommunikation</term>
+ <term name="letter" form="short">brev</term>
+ </terms>
+ </locale>
+ <locale xml:lang="de">
+ <terms>
+ <term name="et-al">et al.</term>
+ <term name="letter">persönliche Kommunikation</term>
+ <term name="letter" form="short">Brief</term>
+ </terms>
+ </locale>
+ <locale xml:lang="el">
+ <terms>
+ <term name="letter">Ï€Ïοσωπική επικοινωνία</term>
+ <term name="letter" form="short">επιστολή</term>
+ </terms>
+ </locale>
+ <locale xml:lang="es">
+ <terms>
+ <term name="from">de</term>
+ <term name="letter">comunicación personal</term>
+ <term name="letter" form="short">carta</term>
+ </terms>
+ </locale>
+ <locale xml:lang="et">
+ <terms>
+ <term name="letter">isiklik suhtlus</term>
+ <term name="letter" form="short">kiri</term>
+ </terms>
+ </locale>
+ <locale xml:lang="eu">
+ <terms>
+ <term name="letter">komunikazio pertsonala</term>
+ <term name="letter" form="short">gutuna</term>
+ </terms>
+ </locale>
+ <locale xml:lang="fa">
+ <terms>
+ <term name="letter">ارتباط شخصی</term>
+ <term name="letter" form="short">نامه</term>
+ </terms>
+ </locale>
+ <locale xml:lang="fi">
+ <terms>
+ <term name="letter">henkilökohtainen viestintä</term>
+ <term name="letter" form="short">kirje</term>
+ </terms>
+ </locale>
+ <locale xml:lang="fr">
+ <terms>
+ <term name="letter">communication personnelle</term>
+ <term name="letter" form="short">lettre</term>
+ <term name="editor" form="short">
+ <single>éd.</single>
+ <multiple>éds.</multiple>
+ </term>
+ </terms>
+ </locale>
+ <locale xml:lang="he">
+ <terms>
+ <term name="letter">תקשורת ×ישית</term>
+ <term name="letter" form="short">מכתב</term>
+ </terms>
+ </locale>
+ <locale xml:lang="hr">
+ <terms>
+ <term name="letter">osobna komunikacija</term>
+ <term name="letter" form="short">pismo</term>
+ </terms>
+ </locale>
+ <locale xml:lang="hu">
+ <terms>
+ <term name="letter">személyes kommunikáció</term>
+ <term name="letter" form="short">levél</term>
+ </terms>
+ </locale>
+ <locale xml:lang="id">
+ <terms>
+ <term name="letter">komunikasi pribadi</term>
+ <term name="letter" form="short">surat</term>
+ </terms>
+ </locale>
+ <locale xml:lang="is">
+ <terms>
+ <term name="letter">persónuleg samskipti</term>
+ <term name="letter" form="short">bréf</term>
+ </terms>
+ </locale>
+ <locale xml:lang="it">
+ <terms>
+ <term name="letter">comunicazione personale</term>
+ <term name="letter" form="short">lettera</term>
+ </terms>
+ </locale>
+ <locale xml:lang="ja">
+ <terms>
+ <term name="letter">個人的ãªã‚„ã‚Šå–ã‚Š</term>
+ <term name="letter" form="short">手紙</term>
+ </terms>
+ </locale>
+ <locale xml:lang="ko">
+ <terms>
+ <term name="letter">ê°œì¸ ì„œì‹ </term>
+ <term name="letter" form="short">편지</term>
+ </terms>
+ </locale>
+ <locale xml:lang="la">
+ <terms>
+ <term name="letter"/>
+ <term name="letter" form="short">epistula</term>
+ </terms>
+ </locale>
+ <locale xml:lang="lt">
+ <terms>
+ <term name="letter">communicationis personalis</term>
+ <term name="letter" form="short"/>
+ </terms>
+ </locale>
+ <locale xml:lang="lv">
+ <terms>
+ <term name="letter">personÄ«ga komunikÄcija</term>
+ <term name="letter" form="short">vēstule</term>
+ </terms>
+ </locale>
+ <locale xml:lang="mn">
+ <terms>
+ <term name="letter">хувийн харилцаа холбоо</term>
+ <term name="letter" form="short">захиа</term>
+ </terms>
+ </locale>
+ <locale xml:lang="nb">
+ <terms>
+ <term name="et-al">et al.</term>
+ <term name="letter">personlig kommunikasjon</term>
+ <term name="letter" form="short">brev</term>
+ </terms>
+ </locale>
+ <locale xml:lang="nl">
+ <terms>
+ <term name="et-al">et al.</term>
+ <term name="letter">persoonlijke communicatie</term>
+ <term name="letter" form="short">brief</term>
+ </terms>
+ </locale>
+ <locale xml:lang="nn">
+ <terms>
+ <term name="et-al">et al.</term>
+ <term name="letter">personlig kommunikasjon</term>
+ <term name="letter" form="short">brev</term>
+ </terms>
+ </locale>
+ <locale xml:lang="pl">
+ <terms>
+ <term name="letter">osobista komunikacja</term>
+ <term name="letter" form="short">list</term>
+ </terms>
+ </locale>
+ <locale xml:lang="pt">
+ <terms>
+ <term name="letter">comunicação pessoal</term>
+ <term name="letter" form="short">carta</term>
+ </terms>
+ </locale>
+ <locale xml:lang="ro">
+ <terms>
+ <term name="letter">comunicare personală</term>
+ <term name="letter" form="short">scrisoare</term>
+ </terms>
+ </locale>
+ <locale xml:lang="ru">
+ <terms>
+ <term name="letter">Ð»Ð¸Ñ‡Ð½Ð°Ñ Ð¿ÐµÑ€ÐµÐ¿Ð¸Ñка</term>
+ <term name="letter" form="short">пиÑьмо</term>
+ </terms>
+ </locale>
+ <locale xml:lang="sk">
+ <terms>
+ <term name="letter">osobná komunikácia</term>
+ <term name="letter" form="short">list</term>
+ </terms>
+ </locale>
+ <locale xml:lang="sl">
+ <terms>
+ <term name="letter">osebna komunikacija</term>
+ <term name="letter" form="short">pismo</term>
+ </terms>
+ </locale>
+ <locale xml:lang="sr">
+ <terms>
+ <term name="letter">лична комуникација</term>
+ <term name="letter" form="short">пиÑмо</term>
+ </terms>
+ </locale>
+ <locale xml:lang="sv">
+ <terms>
+ <term name="letter">personlig kommunikation</term>
+ <term name="letter" form="short">brev</term>
+ </terms>
+ </locale>
+ <locale xml:lang="th">
+ <terms>
+ <term name="letter">à¸à¸²à¸£à¸ªà¸·à¹ˆà¸à¸ªà¸²à¸£à¸ªà¹ˆà¸§à¸™à¸šà¸¸à¸„คล</term>
+ <term name="letter" form="short">จดหมาย</term>
+ </terms>
+ </locale>
+ <locale xml:lang="tr">
+ <terms>
+ <term name="letter">kiÅŸisel iletiÅŸim</term>
+ <term name="letter" form="short">mektup</term>
+ </terms>
+ </locale>
+ <locale xml:lang="uk">
+ <terms>
+ <term name="letter">оÑобиÑте ÑпілкуваннÑ</term>
+ <term name="letter" form="short">лиÑÑ‚</term>
+ </terms>
+ </locale>
+ <locale xml:lang="vi">
+ <terms>
+ <term name="letter">giao tiếp cá nhân</term>
+ <term name="letter" form="short">thÆ°</term>
+ </terms>
+ </locale>
+ <locale xml:lang="zh-CN">
+ <terms>
+ <term name="letter">çš„ç§äººäº¤æµ</term>
+ <term name="letter" form="short">信函</term>
+ </terms>
+ </locale>
+ <locale xml:lang="zh-TW">
+ <terms>
+ <term name="letter">ç§äººé€šè¨Š</term>
+ <term name="letter" form="short">信函</term>
+ </terms>
+ </locale>
+ <!-- General categories of item types:
+ Periodical: article-journal article-magazine article-newspaper post-weblog review review-book
+ Periodical or Booklike: paper-conference
+ Booklike: article book broadcast chapter dataset entry entry-dictionary entry-encyclopedia figure
+ graphic interview manuscript map motion_picture musical_score pamphlet patent
+ personal_communication report song speech thesis post webpage
+ Legal: bill legal_case legislation treaty
+ -->
+ <!-- APA references contain four parts: author, date, title, source -->
+ <macro name="author-bib">
+ <names variable="composer" delimiter=", ">
+ <name name-as-sort-order="all" and="symbol" sort-separator=", " initialize-with=". " delimiter=", " delimiter-precedes-last="always"/>
+ <substitute>
+ <names variable="author"/>
+ <names variable="illustrator"/>
+ <names variable="director">
+ <name name-as-sort-order="all" and="symbol" sort-separator=", " initialize-with=". " delimiter=", " delimiter-precedes-last="always"/>
+ <label form="long" prefix=" (" suffix=")" text-case="title"/>
+ </names>
+ <choose>
+ <if variable="container-title">
+ <choose>
+ <if type="book entry entry-dictionary entry-encyclopedia" match="any">
+ <choose>
+ <if variable="title">
+ <group delimiter=" ">
+ <text macro="title"/>
+ <text macro="parenthetical"/>
+ </group>
+ </if>
+ <else>
+ <text macro="title-and-descriptions"/>
+ </else>
+ </choose>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ <!-- Test for editortranslator and put that first as that becomes available -->
+ <names variable="editor" delimiter=", ">
+ <name name-as-sort-order="all" and="symbol" sort-separator=", " initialize-with=". " delimiter=", " delimiter-precedes-last="always"/>
+ <label form="short" prefix=" (" suffix=")" text-case="title"/>
+ </names>
+ <names variable="editorial-director">
+ <name name-as-sort-order="all" and="symbol" sort-separator=", " initialize-with=". " delimiter=", " delimiter-precedes-last="always"/>
+ <label form="short" prefix=" (" suffix=")" text-case="title"/>
+ </names>
+ <names variable="collection-editor">
+ <name name-as-sort-order="all" and="symbol" sort-separator=", " initialize-with=". " delimiter=", " delimiter-precedes-last="always"/>
+ <label form="short" prefix=" (" suffix=")" text-case="title"/>
+ </names>
+ <choose>
+ <if variable="title">
+ <group delimiter=" ">
+ <text macro="title"/>
+ <text macro="parenthetical"/>
+ </group>
+ </if>
+ <else>
+ <text macro="title-and-descriptions"/>
+ </else>
+ </choose>
+ </substitute>
+ </names>
+ </macro>
+ <macro name="author-intext">
+ <choose>
+ <if type="bill legal_case legislation treaty" match="any">
+ <text macro="title-intext"/>
+ </if>
+ <else-if type="interview personal_communication" match="any">
+ <choose>
+ <!-- These variables indicate that the letter is retrievable by the reader.
+ If not, then use the APA in-text-only personal communication format -->
+ <if variable="archive container-title DOI publisher URL" match="none">
+ <group delimiter=", ">
+ <names variable="author">
+ <name and="symbol" delimiter=", " initialize-with=". "/>
+ <substitute>
+ <text macro="title-intext"/>
+ </substitute>
+ </names>
+ <!-- Replace with term="personal-communication" if that becomes available -->
+ <text term="letter"/>
+ </group>
+ </if>
+ <else>
+ <names variable="author" delimiter=", ">
+ <name form="short" and="symbol" delimiter=", " initialize-with=". "/>
+ <substitute>
+ <text macro="title-intext"/>
+ </substitute>
+ </names>
+ </else>
+ </choose>
+ </else-if>
+ <else>
+ <names variable="composer" delimiter=", ">
+ <name form="short" and="symbol" delimiter=", " initialize-with=". "/>
+ <substitute>
+ <names variable="author"/>
+ <names variable="illustrator"/>
+ <names variable="director"/>
+ <choose>
+ <if variable="container-title">
+ <choose>
+ <if type="book entry entry-dictionary entry-encyclopedia" match="any">
+ <text macro="title-intext"/>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ <names variable="editor"/>
+ <names variable="editorial-director"/>
+ <text macro="title-intext"/>
+ </substitute>
+ </names>
+ </else>
+ </choose>
+ </macro>
+ <macro name="date-bib">
+ <group delimiter=" " prefix="(" suffix=")">
+ <choose>
+ <if is-uncertain-date="issued">
+ <text term="circa" form="short"/>
+ </if>
+ </choose>
+ <group>
+ <choose>
+ <if variable="issued">
+ <date variable="issued">
+ <date-part name="year"/>
+ </date>
+ <text variable="year-suffix"/>
+ <choose>
+ <if type="article-magazine article-newspaper broadcast interview motion_picture pamphlet personal_communication post post-weblog song speech webpage" match="any">
+ <!-- Many video and audio examples in manual give full dates. Err on the side of too much information. -->
+ <date variable="issued">
+ <date-part prefix=", " name="month"/>
+ <date-part prefix=" " name="day"/>
+ </date>
+ </if>
+ <else-if type="paper-conference">
+ <!-- Capture 'speech' stored as 'paper-conference' -->
+ <choose>
+ <if variable="collection-editor editor editorial-director issue page volume" match="none">
+ <date variable="issued">
+ <date-part prefix=", " name="month"/>
+ <date-part prefix=" " name="day"/>
+ </date>
+ </if>
+ </choose>
+ </else-if>
+ <!-- Only year: article article-journal book chapter entry entry-dictionary entry-encyclopedia dataset figure graphic
+ manuscript map musical_score paper-conference[published] patent report review review-book thesis -->
+ </choose>
+ </if>
+ <else-if variable="status">
+ <group>
+ <text variable="status" text-case="lowercase"/>
+ <text variable="year-suffix" prefix="-"/>
+ </group>
+ </else-if>
+ <else>
+ <text term="no date" form="short"/>
+ <text variable="year-suffix" prefix="-"/>
+ </else>
+ </choose>
+ </group>
+ </group>
+ </macro>
+ <macro name="date-sort-group">
+ <!-- APA sorts 1. no-date items, 2. items with dates, 3. in-press (status) items -->
+ <choose>
+ <if variable="issued">
+ <text value="1"/>
+ </if>
+ <else-if variable="status">
+ <text value="2"/>
+ </else-if>
+ <else>
+ <text value="0"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="date-sort-date">
+ <date variable="issued" form="numeric"/>
+ </macro>
+ <macro name="date-intext">
+ <choose>
+ <if variable="issued">
+ <group delimiter="/">
+ <group delimiter=" ">
+ <choose>
+ <if is-uncertain-date="original-date">
+ <text term="circa" form="short"/>
+ </if>
+ </choose>
+ <date variable="original-date">
+ <date-part name="year"/>
+ </date>
+ </group>
+ <group delimiter=" ">
+ <choose>
+ <if is-uncertain-date="issued">
+ <text term="circa" form="short"/>
+ </if>
+ </choose>
+ <group>
+ <choose>
+ <if type="interview personal_communication" match="any">
+ <choose>
+ <if variable="archive container-title DOI publisher URL" match="none">
+ <!-- These variables indicate that the communication is retrievable by the reader.
+ If not, then use the in-text-only personal communication format -->
+ <date variable="issued" form="text"/>
+ </if>
+ <else>
+ <date variable="issued">
+ <date-part name="year"/>
+ </date>
+ </else>
+ </choose>
+ </if>
+ <else>
+ <date variable="issued">
+ <date-part name="year"/>
+ </date>
+ </else>
+ </choose>
+ <text variable="year-suffix"/>
+ </group>
+ </group>
+ </group>
+ </if>
+ <else-if variable="status">
+ <text variable="status" text-case="lowercase"/>
+ <text variable="year-suffix" prefix="-"/>
+ </else-if>
+ <else>
+ <text term="no date" form="short"/>
+ <text variable="year-suffix" prefix="-"/>
+ </else>
+ </choose>
+ </macro>
+ <!-- APA has two description elements following the title:
+ title (parenthetical) [bracketed] -->
+ <macro name="title-and-descriptions">
+ <choose>
+ <if variable="title">
+ <group delimiter=" ">
+ <text macro="title"/>
+ <text macro="parenthetical"/>
+ <text macro="bracketed"/>
+ </group>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <text macro="bracketed"/>
+ <text macro="parenthetical"/>
+ </group>
+ </else>
+ </choose>
+ </macro>
+ <macro name="title">
+ <choose>
+ <if type="post webpage" match="any">
+ <!-- Webpages are always italicized -->
+ <text variable="title" font-style="italic"/>
+ </if>
+ <else-if variable="container-title" match="any">
+ <!-- Other types are italicized based on presence of container-title.
+ Assume that review and review-book are published in periodicals/blogs,
+ not just on a web page (ex. 69) -->
+ <text variable="title"/>
+ </else-if>
+ <else>
+ <choose>
+ <if type="article-journal article-magazine article-newspaper post-weblog review review-book" match="any">
+ <text variable="title" font-style="italic"/>
+ </if>
+ <else-if type="paper-conference">
+ <choose>
+ <if variable="collection-editor editor editorial-director" match="any">
+ <group delimiter=": " font-style="italic">
+ <text variable="title"/>
+ <!-- Replace with volume-title as that becomes available -->
+ <choose>
+ <if is-numeric="volume" match="none">
+ <group delimiter=" ">
+ <label variable="volume" form="short" text-case="capitalize-first"/>
+ <text variable="volume"/>
+ </group>
+ </if>
+ </choose>
+ </group>
+ </if>
+ <else>
+ <text variable="title" font-style="italic"/>
+ </else>
+ </choose>
+ </else-if>
+ <else>
+ <group delimiter=": " font-style="italic">
+ <text variable="title"/>
+ <!-- Replace with volume-title as that becomes available -->
+ <choose>
+ <if is-numeric="volume" match="none">
+ <group delimiter=" ">
+ <label variable="volume" form="short" text-case="capitalize-first"/>
+ <text variable="volume"/>
+ </group>
+ </if>
+ </choose>
+ </group>
+ </else>
+ </choose>
+ </else>
+ </choose>
+ </macro>
+ <macro name="title-intext">
+ <choose>
+ <if variable="title" match="none">
+ <text macro="bracketed-intext" prefix="[" suffix="]"/>
+ </if>
+ <else-if type="bill">
+ <!-- If a bill has no number or container-title, assume it is a hearing; italic -->
+ <choose>
+ <if variable="number container-title" match="none">
+ <text variable="title" form="short" font-style="italic" text-case="title"/>
+ </if>
+ <else-if variable="title">
+ <text variable="title" form="short" text-case="title"/>
+ </else-if>
+ <else>
+ <group delimiter=" ">
+ <text variable="genre"/>
+ <group delimiter=" ">
+ <choose>
+ <if variable="chapter-number container-title" match="none">
+ <!-- Replace with label variable="number" as that becomes available -->
+ <text term="issue" form="short"/>
+ </if>
+ </choose>
+ <text variable="number"/>
+ </group>
+ </group>
+ </else>
+ </choose>
+ </else-if>
+ <else-if type="legal_case" match="any">
+ <!-- Cases are italicized -->
+ <text variable="title" font-style="italic"/>
+ </else-if>
+ <else-if type="legislation treaty" match="any">
+ <!-- Legislation and treaties not italicized or quoted -->
+ <text variable="title" form="short" text-case="title"/>
+ </else-if>
+ <else-if type="post webpage" match="any">
+ <!-- Webpages are always italicized -->
+ <text variable="title" form="short" font-style="italic" text-case="title"/>
+ </else-if>
+ <else-if variable="container-title" match="any">
+ <!-- Other types are italicized or quoted based on presence of container-title. As in title macro. -->
+ <text variable="title" form="short" quotes="true" text-case="title"/>
+ </else-if>
+ <else>
+ <text variable="title" form="short" font-style="italic" text-case="title"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="parenthetical">
+ <!-- (Secondary contributors; Database location; Genre no. 123; Report Series 123, Version, Edition, Volume, Page) -->
+ <group prefix="(" suffix=")">
+ <choose>
+ <if type="patent">
+ <!-- authority: U.S. ; genre: patent ; number: 123,445 -->
+ <group delimiter=" ">
+ <text variable="authority" form="short"/>
+ <choose>
+ <if variable="genre">
+ <text variable="genre" text-case="capitalize-first"/>
+ </if>
+ <else>
+ <!-- This should be localized -->
+ <text value="patent" text-case="capitalize-first"/>
+ </else>
+ </choose>
+ <group delimiter=" ">
+ <!-- Replace with label variable="number" if that becomes available -->
+ <text term="issue" form="short" text-case="capitalize-first"/>
+ <text variable="number"/>
+ </group>
+ </group>
+ </if>
+ <else-if type="post webpage" match="any">
+ <!-- For post webpage, container-title is treated as publisher -->
+ <group delimiter="; ">
+ <text macro="secondary-contributors"/>
+ <text macro="database-location"/>
+ <text macro="number"/>
+ <text macro="locators-booklike"/>
+ </group>
+ </else-if>
+ <else-if variable="container-title">
+ <group delimiter="; ">
+ <text macro="secondary-contributors"/>
+ <choose>
+ <if type="broadcast graphic map motion_picture song" match="any">
+ <!-- For audiovisual media, number information comes after title, not container-title -->
+ <text macro="number"/>
+ </if>
+ </choose>
+ </group>
+ </else-if>
+ <else>
+ <group delimiter="; ">
+ <text macro="secondary-contributors"/>
+ <text macro="database-location"/>
+ <text macro="number"/>
+ <text macro="locators-booklike"/>
+ </group>
+ </else>
+ </choose>
+ </group>
+ </macro>
+ <macro name="parenthetical-container">
+ <choose>
+ <if variable="container-title" match="any">
+ <group prefix="(" suffix=")">
+ <group delimiter="; ">
+ <text macro="database-location"/>
+ <choose>
+ <if type="broadcast graphic map motion_picture song" match="none">
+ <!-- For audiovisual media, number information comes after title, not container-title -->
+ <text macro="number"/>
+ </if>
+ </choose>
+ <text macro="locators-booklike"/>
+ </group>
+ </group>
+ </if>
+ </choose>
+ </macro>
+ <macro name="bracketed">
+ <!-- [Descriptive information] -->
+ <!-- If there is a number, genre is already printed in macro="number" -->
+ <group prefix="[" suffix="]">
+ <choose>
+ <if variable="reviewed-author reviewed-title" type="review review-book" match="any">
+ <!-- Reviewed item -->
+ <group delimiter="; ">
+ <group delimiter=", ">
+ <group delimiter=" ">
+ <!-- Assume that genre is entered as 'Review of the book' or similar -->
+ <choose>
+ <if variable="number" match="none">
+ <choose>
+ <if variable="genre">
+ <text variable="genre" text-case="capitalize-first"/>
+ </if>
+ <else-if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ </else-if>
+ <else>
+ <!-- Replace with term="review" as that becomes available -->
+ <text value="Review of"/>
+ </else>
+ </choose>
+ </if>
+ <else>
+ <choose>
+ <if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ </if>
+ <else>
+ <!-- Replace with term="review" as that becomes available -->
+ <text value="Review of"/>
+ </else>
+ </choose>
+ </else>
+ </choose>
+ <text macro="reviewed-title"/>
+ </group>
+ <names variable="reviewed-author">
+ <label form="verb-short" suffix=" "/>
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </group>
+ <choose>
+ <if variable="genre" match="any">
+ <choose>
+ <if variable="number" match="none">
+ <text variable="medium" text-case="capitalize-first"/>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ </group>
+ </if>
+ <else-if type="thesis">
+ <!-- Thesis type and institution -->
+ <group delimiter="; ">
+ <choose>
+ <if variable="number" match="none">
+ <group delimiter=", ">
+ <text variable="genre" text-case="capitalize-first"/>
+ <choose>
+ <if variable="archive DOI URL" match="any">
+ <!-- Include the university in brackets if thesis is published -->
+ <text variable="publisher"/>
+ </if>
+ </choose>
+ </group>
+ </if>
+ </choose>
+ <text variable="medium" text-case="capitalize-first"/>
+ </group>
+ </else-if>
+ <else-if variable="interviewer" type="interview" match="any">
+ <!-- Interview information -->
+ <choose>
+ <if variable="title">
+ <text macro="format"/>
+ </if>
+ <else-if variable="genre">
+ <group delimiter="; ">
+ <group delimiter=" ">
+ <text variable="genre" text-case="capitalize-first"/>
+ <group delimiter=" ">
+ <text term="author" form="verb"/>
+ <names variable="interviewer">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </group>
+ </group>
+ </group>
+ </else-if>
+ <else-if variable="interviewer">
+ <group delimiter="; ">
+ <names variable="interviewer">
+ <label form="verb" suffix=" " text-case="capitalize-first"/>
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ <text variable="medium" text-case="capitalize-first"/>
+ </group>
+ </else-if>
+ <else>
+ <text macro="format"/>
+ </else>
+ </choose>
+ </else-if>
+ <else-if type="personal_communication">
+ <!-- Letter information -->
+ <choose>
+ <if variable="recipient">
+ <group delimiter="; ">
+ <group delimiter=" ">
+ <choose>
+ <if variable="number" match="none">
+ <choose>
+ <if variable="genre">
+ <text variable="genre" text-case="capitalize-first"/>
+ </if>
+ <else-if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ </else-if>
+ <else>
+ <text term="letter" form="short" text-case="capitalize-first"/>
+ </else>
+ </choose>
+ </if>
+ <else>
+ <choose>
+ <if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ </if>
+ <else>
+ <text term="letter" form="short" text-case="capitalize-first"/>
+ </else>
+ </choose>
+ </else>
+ </choose>
+ <names variable="recipient" delimiter=", ">
+ <label form="verb" suffix=" "/>
+ <name and="symbol" delimiter=", "/>
+ </names>
+ </group>
+ <choose>
+ <if variable="genre" match="any">
+ <choose>
+ <if variable="number" match="none">
+ <text variable="medium" text-case="capitalize-first"/>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ </group>
+ </if>
+ <else>
+ <text macro="format"/>
+ </else>
+ </choose>
+ </else-if>
+ <else-if variable="composer" type="song" match="all">
+ <!-- Performer of classical music works -->
+ <group delimiter="; ">
+ <choose>
+ <if variable="number" match="none">
+ <group delimiter=" ">
+ <choose>
+ <if variable="genre">
+ <text variable="genre" text-case="capitalize-first"/>
+ <!-- Replace prefix with performer label as that becomes available -->
+ <names variable="author" prefix="recorded by ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </if>
+ <else-if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ <!-- Replace prefix with performer label as that becomes available -->
+ <names variable="author" prefix="recorded by ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </else-if>
+ <else>
+ <!-- Replace prefix with performer label as that becomes available -->
+ <names variable="author" prefix="Recorded by ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </else>
+ </choose>
+ </group>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <choose>
+ <if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ <!-- Replace prefix with performer label as that becomes available -->
+ <names variable="author" prefix="recorded by ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </if>
+ <else>
+ <!-- Replace prefix with performer label as that becomes available -->
+ <names variable="author" prefix="Recorded by ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ </else>
+ </choose>
+ </group>
+ </else>
+ </choose>
+ <choose>
+ <if variable="genre" match="any">
+ <choose>
+ <if variable="number" match="none">
+ <text variable="medium" text-case="capitalize-first"/>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ </group>
+ </else-if>
+ <else-if variable="container-title" match="none">
+ <!-- Other description -->
+ <text macro="format"/>
+ </else-if>
+ <else>
+ <!-- For conference presentations, chapters in reports, software, place bracketed after the container title -->
+ <choose>
+ <if type="paper-conference speech" match="any">
+ <choose>
+ <if variable="collection-editor editor editorial-director issue page volume" match="any">
+ <text macro="format"/>
+ </if>
+ </choose>
+ </if>
+ <else-if type="book">
+ <choose>
+ <if variable="version" match="none">
+ <text macro="format"/>
+ </if>
+ </choose>
+ </else-if>
+ <else-if type="report" match="none">
+ <text macro="format"/>
+ </else-if>
+ </choose>
+ </else>
+ </choose>
+ </group>
+ </macro>
+ <macro name="bracketed-intext">
+ <group prefix="[" suffix="]">
+ <choose>
+ <if variable="reviewed-author reviewed-title" type="review review-book" match="any">
+ <!-- This should be localized -->
+ <text macro="reviewed-title-intext" prefix="Review of "/>
+ </if>
+ <else-if variable="interviewer" type="interview" match="any">
+ <names variable="interviewer">
+ <label form="verb" suffix=" " text-case="capitalize-first"/>
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <substitute>
+ <text macro="format-intext"/>
+ </substitute>
+ </names>
+ </else-if>
+ <else-if type="personal_communication">
+ <!-- Letter information -->
+ <choose>
+ <if variable="recipient">
+ <group delimiter=" ">
+ <choose>
+ <if variable="number" match="none">
+ <text variable="genre" text-case="capitalize-first"/>
+ </if>
+ <else>
+ <text term="letter" form="short" text-case="capitalize-first"/>
+ </else>
+ </choose>
+ <names variable="recipient" delimiter=", ">
+ <label form="verb" suffix=" "/>
+ <name and="symbol" delimiter=", "/>
+ </names>
+ </group>
+ </if>
+ <else>
+ <text macro="format-intext"/>
+ </else>
+ </choose>
+ </else-if>
+ <else>
+ <text macro="format-intext"/>
+ </else>
+ </choose>
+ </group>
+ </macro>
+ <macro name="bracketed-container">
+ <group prefix="[" suffix="]">
+ <choose>
+ <if type="paper-conference speech" match="any">
+ <!-- Conference presentations should describe the session [container] in bracketed unless published in a proceedings -->
+ <choose>
+ <if variable="collection-editor editor editorial-director issue page volume" match="none">
+ <text macro="format"/>
+ </if>
+ </choose>
+ </if>
+ <else-if type="book" variable="version" match="all">
+ <!-- For entries in mobile app reference works, place bracketed after the container-title -->
+ <text macro="format"/>
+ </else-if>
+ <else-if type="report">
+ <!-- For chapters in reports, place bracketed after the container title -->
+ <text macro="format"/>
+ </else-if>
+ </choose>
+ </group>
+ </macro>
+ <macro name="secondary-contributors">
+ <choose>
+ <if type="article-journal article-magazine article-newspaper post-weblog review review-book" match="any">
+ <text macro="secondary-contributors-periodical"/>
+ </if>
+ <else-if type="paper-conference">
+ <choose>
+ <if variable="collection-editor editor editorial-director" match="any">
+ <text macro="secondary-contributors-booklike"/>
+ </if>
+ <else>
+ <text macro="secondary-contributors-periodical"/>
+ </else>
+ </choose>
+ </else-if>
+ <else>
+ <text macro="secondary-contributors-booklike"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="secondary-contributors-periodical">
+ <group delimiter="; ">
+ <choose>
+ <if variable="title">
+ <names variable="interviewer" delimiter="; ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <label form="short" prefix=", " text-case="title"/>
+ </names>
+ </if>
+ </choose>
+ <names variable="translator" delimiter="; ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <label form="short" prefix=", " text-case="title"/>
+ </names>
+ </group>
+ </macro>
+ <macro name="secondary-contributors-booklike">
+ <group delimiter="; ">
+ <choose>
+ <if variable="title">
+ <names variable="interviewer">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <label form="short" prefix=", " text-case="title"/>
+ </names>
+ </if>
+ </choose>
+ <!-- When editortranslator becomes available, add a test: variable="editortranslator" match="none"; then print translator -->
+ <choose>
+ <if type="post webpage" match="none">
+ <!-- Webpages treat container-title like publisher -->
+ <choose>
+ <if variable="container-title" match="none">
+ <group delimiter="; ">
+ <names variable="container-author">
+ <label form="verb-short" suffix=" " text-case="title"/>
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ <names variable="editor translator" delimiter="; ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <label form="short" prefix=", " text-case="title"/>
+ </names>
+ </group>
+ </if>
+ </choose>
+ </if>
+ <else>
+ <group delimiter="; ">
+ <names variable="container-author">
+ <label form="verb-short" suffix=" " text-case="title"/>
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ </names>
+ <names variable="editor translator" delimiter="; ">
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <label form="short" prefix=", " text-case="title"/>
+ </names>
+ </group>
+ </else>
+ </choose>
+ </group>
+ </macro>
+ <macro name="database-location">
+ <choose>
+ <if variable="archive-place" match="none">
+ <!-- With `archive-place`: physical archives. Without: online archives. -->
+ <!-- Add archive_collection as that becomes available -->
+ <text variable="archive_location"/>
+ </if>
+ </choose>
+ </macro>
+ <macro name="number">
+ <choose>
+ <if variable="number">
+ <group delimiter=", ">
+ <group delimiter=" ">
+ <text variable="genre" text-case="title"/>
+ <choose>
+ <if is-numeric="number">
+ <!-- Replace with label variable="number" if that becomes available -->
+ <text term="issue" form="short" text-case="capitalize-first"/>
+ <text variable="number"/>
+ </if>
+ <else>
+ <text variable="number"/>
+ </else>
+ </choose>
+ </group>
+ <choose>
+ <if type="thesis">
+ <choose>
+ <!-- Include the university in brackets if thesis is published -->
+ <if variable="archive DOI URL" match="any">
+ <text variable="publisher"/>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ </group>
+ </if>
+ </choose>
+ </macro>
+ <macro name="locators-booklike">
+ <choose>
+ <if type="article-journal article-magazine article-newspaper broadcast interview patent post post-weblog review review-book speech webpage" match="any"/>
+ <else-if type="paper-conference">
+ <choose>
+ <if variable="collection-editor editor editorial-director" match="any">
+ <group delimiter=", ">
+ <text macro="version"/>
+ <text macro="edition"/>
+ <text macro="volume-booklike"/>
+ </group>
+ </if>
+ </choose>
+ </else-if>
+ <else>
+ <group delimiter=", ">
+ <text macro="version"/>
+ <text macro="edition"/>
+ <text macro="volume-booklike"/>
+ </group>
+ </else>
+ </choose>
+ </macro>
+ <macro name="version">
+ <choose>
+ <if is-numeric="version">
+ <group delimiter=" ">
+ <!-- replace with label variable="version" if that becomes available -->
+ <text term="version" text-case="capitalize-first"/>
+ <text variable="version"/>
+ </group>
+ </if>
+ <else>
+ <text variable="version"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="edition">
+ <choose>
+ <if is-numeric="edition">
+ <group delimiter=" ">
+ <number variable="edition" form="ordinal"/>
+ <label variable="edition" form="short"/>
+ </group>
+ </if>
+ <else>
+ <text variable="edition"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="volume-booklike">
+ <group delimiter=", ">
+ <!-- Report series [ex. 52] -->
+ <choose>
+ <if type="report">
+ <group delimiter=" ">
+ <text variable="collection-title" text-case="title"/>
+ <text variable="collection-number"/>
+ </group>
+ </if>
+ </choose>
+ <choose>
+ <if variable="volume" match="any">
+ <choose>
+ <!-- Non-numeric volumes are already printed as part of the book title -->
+ <if is-numeric="volume" match="none"/>
+ <else>
+ <group delimiter=" ">
+ <label variable="volume" form="short" text-case="capitalize-first"/>
+ <number variable="volume" form="numeric"/>
+ </group>
+ </else>
+ </choose>
+ </if>
+ <else>
+ <group>
+ <!-- Replace with label variable="number-of-volumes" if that becomes available -->
+ <text term="volume" form="short" text-case="capitalize-first" suffix=" "/>
+ <text term="page-range-delimiter" prefix="1"/>
+ <number variable="number-of-volumes" form="numeric"/>
+ </group>
+ </else>
+ </choose>
+ <group delimiter=" ">
+ <label variable="issue" text-case="capitalize-first"/>
+ <text variable="issue"/>
+ </group>
+ <group delimiter=" ">
+ <label variable="page" form="short" suffix=" "/>
+ <text variable="page"/>
+ </group>
+ </group>
+ </macro>
+ <macro name="reviewed-title">
+ <choose>
+ <if variable="reviewed-title">
+ <!-- Not possible to distinguish TV series episode from other reviewed
+ works [Ex. 69] -->
+ <text variable="reviewed-title" font-style="italic"/>
+ </if>
+ <else>
+ <!-- Assume title is title of reviewed work -->
+ <text variable="title" font-style="italic"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="reviewed-title-intext">
+ <choose>
+ <if variable="reviewed-title">
+ <!-- Not possible to distinguish TV series episode from other reviewed works [Ex. 69] -->
+ <text variable="reviewed-title" form="short" font-style="italic" text-case="title"/>
+ </if>
+ <else>
+ <!-- Assume title is title of reviewed work -->
+ <text variable="title" form="short" font-style="italic" text-case="title"/>
+ </else>
+ </choose>
+ </macro>
+ <macro name="format">
+ <choose>
+ <if variable="genre medium" match="any">
+ <group delimiter="; ">
+ <choose>
+ <if variable="number" match="none">
+ <text variable="genre" text-case="capitalize-first"/>
+ </if>
+ </choose>
+ <text variable="medium" text-case="capitalize-first"/>
+ </group>
+ </if>
+ <!-- Generic labels for specific types -->
+ <!-- These should be localized when possible -->
+ <else-if type="dataset">
+ <text value="Data set"/>
+ </else-if>
+ <else-if type="book" variable="version" match="all">
+ <!-- Replace with type="software" and term="software" as that becomes available -->
+ <text value="Computer software"/>
+ </else-if>
+ <else-if type="interview personal_communication" match="any">
+ <choose>
+ <if variable="archive container-title DOI publisher URL" match="none">
+ <text term="letter" text-case="capitalize-first"/>
+ </if>
+ <else-if type="interview">
+ <text term="interview" text-case="capitalize-first"/>
+ </else-if>
+ </choose>
+ </else-if>
+ <else-if type="map">
+ <text value="Map"/>
+ </else-if>
+ </choose>
+ </macro>
+ <macro name="format-intext">
+ <choose>
+ <if variable="genre" match="any">
+ <text variable="genre" text-case="capitalize-first"/>
+ </if>
+ <else-if variable="medium">
+ <text variable="medium" text-case="capitalize-first"/>
+ </else-if>
+ <!-- Generic labels for specific types -->
+ <!-- These should be localized when possible -->
+ <else-if type="dataset">
+ <text value="Data set"/>
+ </else-if>
+ <else-if type="book" variable="version" match="all">
+ <!-- Replace with type="software" and term="software" as that becomes available -->
+ <text value="Computer software"/>
+ </else-if>
+ <else-if type="interview personal_communication" match="any">
+ <choose>
+ <if variable="archive container-title DOI publisher URL" match="none">
+ <text term="letter" text-case="capitalize-first"/>
+ </if>
+ <else-if type="interview">
+ <text term="interview" text-case="capitalize-first"/>
+ </else-if>
+ </choose>
+ </else-if>
+ <else-if type="map">
+ <text value="Map"/>
+ </else-if>
+ </choose>
+ </macro>
+ <!-- APA 'source' element contains four parts:
+ container, event, publisher, access -->
+ <macro name="container">
+ <choose>
+ <if type="article-journal article-magazine article-newspaper post-weblog review review-book" match="any">
+ <!-- Periodical items -->
+ <text macro="container-periodical"/>
+ </if>
+ <else-if type="paper-conference">
+ <!-- Determine if paper-conference is a periodical or booklike -->
+ <choose>
+ <if variable="editor editorial-director collection-editor container-author" match="any">
+ <text macro="container-booklike"/>
+ </if>
+ <else>
+ <text macro="container-periodical"/>
+ </else>
+ </choose>
+ </else-if>
+ <else-if type="post webpage" match="none">
+ <!-- post and webpage treat container-title like publisher -->
+ <text macro="container-booklike"/>
+ </else-if>
+ </choose>
+ </macro>
+ <macro name="container-periodical">
+ <group delimiter=". ">
+ <group delimiter=", ">
+ <text variable="container-title" font-style="italic" text-case="title"/>
+ <choose>
+ <if variable="volume">
+ <group>
+ <text variable="volume" font-style="italic"/>
+ <text variable="issue" prefix="(" suffix=")"/>
+ </group>
+ </if>
+ <else>
+ <text variable="issue" font-style="italic"/>
+ </else>
+ </choose>
+ <choose>
+ <if variable="page">
+ <text variable="page"/>
+ </if>
+ <else>
+ <!-- Ex. 6: Journal article with article number or eLocator -->
+ <!-- This should be localized -->
+ <text variable="number" prefix="Article "/>
+ </else>
+ </choose>
+ </group>
+ <choose>
+ <if variable="issued">
+ <choose>
+ <if variable="issue page volume" match="none">
+ <text variable="status" text-case="capitalize-first"/>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ </group>
+ </macro>
+ <macro name="container-booklike">
+ <choose>
+ <if variable="container-title" match="any">
+ <group delimiter=" ">
+ <text term="in" text-case="capitalize-first"/>
+ <group delimiter=", ">
+ <names variable="editor translator" delimiter=", & ">
+ <!-- Change to editortranslator and move editor to substitute as that becomes available -->
+ <name and="symbol" initialize-with=". " delimiter=", "/>
+ <label form="short" text-case="title" prefix=" (" suffix=")"/>
+ <substitute>
+ <names variable="editorial-director"/>
+ <names variable="collection-editor"/>
+ <names variable="container-author"/>
+ </substitute>
+ </names>
+ <group delimiter=": " font-style="italic">
+ <text variable="container-title"/>
+ <!-- Replace with volume-title as that becomes available -->
+ <choose>
+ <if is-numeric="volume" match="none">
+ <group delimiter=" ">
+ <label variable="volume" form="short" text-case="capitalize-first"/>
+ <text variable="volume"/>
+ </group>
+ </if>
+ </choose>
+ </group>
+ </group>
+ <text macro="parenthetical-container"/>
+ <text macro="bracketed-container"/>
+ </group>
+ </if>
+ </choose>
+ </macro>
+ <macro name="publisher">
+ <group delimiter="; ">
+ <choose>
+ <if type="thesis">
+ <choose>
+ <if variable="archive DOI URL" match="none">
+ <text variable="publisher"/>
+ </if>
+ </choose>
+ </if>
+ <else-if type="post webpage" match="any">
+ <!-- For websites, treat container title like publisher -->
+ <group delimiter="; ">
+ <text variable="container-title" text-case="title"/>
+ <text variable="publisher"/>
+ </group>
+ </else-if>
+ <else-if type="paper-conference">
+ <!-- For paper-conference, don't print publisher if in a journal-like proceedings -->
+ <choose>
+ <if variable="collection-editor editor editorial-director" match="any">
+ <text variable="publisher"/>
+ </if>
+ </choose>
+ </else-if>
+ <else-if type="article-journal article-magazine article-newspaper post-weblog" match="none">
+ <text variable="publisher"/>
+ </else-if>
+ </choose>
+ <group delimiter=", ">
+ <choose>
+ <if variable="archive-place">
+ <!-- With `archive-place`: physical archives. Without: online archives. -->
+ <!-- For physical archives, print the location before the archive name.
+ For electronic archives, these are printed in macro="description". -->
+ <!-- Split "archive_location" into "archive_collection" and "archive_location" as that becomes available -->
+ <!-- Must test for archive_collection:
+ With collection: archive_collection (archive_location), archive, archive-place
+ No collection: archive (archive_location), archive-place
+ -->
+ <text variable="archive_location"/>
+ </if>
+ </choose>
+ <text variable="archive"/>
+ <text variable="archive-place"/>
+ </group>
+ </group>
+ </macro>
+ <macro name="access">
+ <choose>
+ <if variable="DOI" match="any">
+ <text variable="DOI" prefix="https://doi.org/"/>
+ </if>
+ <else-if variable="URL">
+ <group delimiter=" ">
+ <choose>
+ <if variable="issued status" match="none">
+ <group delimiter=" ">
+ <text term="retrieved" text-case="capitalize-first"/>
+ <date variable="accessed" form="text" suffix=","/>
+ <text term="from"/>
+ </group>
+ </if>
+ </choose>
+ <text variable="URL"/>
+ </group>
+ </else-if>
+ </choose>
+ </macro>
+ <macro name="event">
+ <choose>
+ <if variable="event">
+ <!-- To prevent Zotero from printing event-place due to its double-mapping of all 'place' to
+ both publisher-place and event-place. Remove this 'choose' when that is changed. -->
+ <choose>
+ <if variable="collection-editor editor editorial-director issue page volume" match="none">
+ <!-- Don't print event info if published in a proceedings -->
+ <group delimiter=", ">
+ <text variable="event"/>
+ <text variable="event-place"/>
+ </group>
+ </if>
+ </choose>
+ </if>
+ </choose>
+ </macro>
+ <!-- After 'source', APA also prints publication history (original publication, reprint info, retraction info) -->
+ <macro name="publication-history">
+ <choose>
+ <if type="patent" match="none">
+ <group prefix="(" suffix=")">
+ <choose>
+ <if variable="references">
+ <!-- This provides the option for more elaborate description
+ of publication history, such as full "reprinted" references
+ (examples 11, 43, 44) or retracted references -->
+ <text variable="references"/>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <text value="Original work published"/>
+ <choose>
+ <if is-uncertain-date="original-date">
+ <text term="circa" form="short"/>
+ </if>
+ </choose>
+ <date variable="original-date">
+ <date-part name="year"/>
+ </date>
+ </group>
+ </else>
+ </choose>
+ </group>
+ </if>
+ <else>
+ <text variable="references" prefix="(" suffix=")"/>
+ </else>
+ </choose>
+ </macro>
+ <!-- Legal citations have their own rules -->
+ <macro name="legal-cites">
+ <choose>
+ <if type="legal_case">
+ <group delimiter=". ">
+ <group delimiter=", ">
+ <text variable="title"/>
+ <group delimiter=" ">
+ <text macro="container-legal"/>
+ <text macro="date-legal"/>
+ </group>
+ <text variable="references"/>
+ </group>
+ <text macro="access"/>
+ </group>
+ </if>
+ <else-if type="bill">
+ <!-- Currently designed to handle bills, resolutions, hearings, rederal reports. -->
+ <group delimiter=". ">
+ <group delimiter=", ">
+ <choose>
+ <if variable="number container-title" match="none">
+ <!-- If no number or container-title, then assume it is a hearing -->
+ <text variable="title" font-style="italic"/>
+ </if>
+ <else>
+ <text variable="title"/>
+ </else>
+ </choose>
+ <group delimiter=" ">
+ <text macro="container-legal"/>
+ <text macro="date-legal"/>
+ <choose>
+ <if variable="number container-title" match="none">
+ <!-- If no number or container-title, then assume it is a hearing -->
+ <names variable="author" prefix="(testimony of " suffix=")">
+ <name and="symbol" delimiter=", "/>
+ </names>
+ </if>
+ <else>
+ <text variable="status" prefix="(" suffix=")"/>
+ </else>
+ </choose>
+ </group>
+ <text variable="references"/>
+ </group>
+ <text macro="access"/>
+ </group>
+ </else-if>
+ <else-if type="legislation">
+ <!-- Currently designed to handle statutes, codified regulations, executive orders.
+ For uncodified regulations, assume future code section is in status. -->
+ <group delimiter=". ">
+ <group delimiter=", ">
+ <text variable="title"/>
+ <group delimiter=" ">
+ <text macro="container-legal"/>
+ <text macro="date-legal"/>
+ <text variable="status" prefix="(" suffix=")"/>
+ </group>
+ <text variable="references"/>
+ </group>
+ <text macro="access"/>
+ </group>
+ </else-if>
+ <else-if type="treaty">
+ <!-- APA generally defers to Bluebook for legal citations, but diverges without
+ explanation for treaty items. The Bluebook format that was used in APA 6th
+ ed. is used here. -->
+ <group delimiter=", ">
+ <text variable="title" text-case="title"/>
+ <names variable="author">
+ <name initialize-with="." form="short" delimiter="-"/>
+ </names>
+ <text macro="date-legal"/>
+ <text macro="container-legal"/>
+ <text macro="access"/>
+ </group>
+ </else-if>
+ </choose>
+ </macro>
+ <macro name="date-legal">
+ <choose>
+ <if type="legal_case">
+ <group prefix="(" suffix=")" delimiter=" ">
+ <text variable="authority"/>
+ <choose>
+ <if variable="container-title" match="any">
+ <!-- Print only year for cases published in reporters-->
+ <date variable="issued" form="numeric" date-parts="year"/>
+ </if>
+ <else>
+ <date variable="issued" form="text"/>
+ </else>
+ </choose>
+ </group>
+ </if>
+ <else-if type="bill legislation" match="any">
+ <group prefix="(" suffix=")" delimiter=" ">
+ <group delimiter=" ">
+ <date variable="original-date">
+ <date-part name="year"/>
+ </date>
+ <text term="and" form="symbol"/>
+ </group>
+ <date variable="issued">
+ <date-part name="year"/>
+ </date>
+ </group>
+ </else-if>
+ <else-if type="treaty">
+ <date variable="issued" form="text"/>
+ </else-if>
+ </choose>
+ </macro>
+ <macro name="container-legal">
+ <!-- Expect legal item container-titles to be stored in short form -->
+ <choose>
+ <if type="legal_case">
+ <group delimiter=" ">
+ <choose>
+ <if variable="container-title">
+ <group delimiter=" ">
+ <text variable="volume"/>
+ <text variable="container-title"/>
+ <group delimiter=" ">
+ <!-- Change to label variable="section" as that becomes available -->
+ <text term="section" form="symbol"/>
+ <text variable="section"/>
+ </group>
+ <choose>
+ <if variable="page page-first" match="any">
+ <text variable="page-first"/>
+ </if>
+ <else>
+ <text value="___"/>
+ </else>
+ </choose>
+ </group>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <choose>
+ <if is-numeric="number">
+ <!-- Replace with label variable="number" if that becomes available -->
+ <text term="issue" form="short" text-case="capitalize-first"/>
+ </if>
+ </choose>
+ <text variable="number"/>
+ </group>
+ </else>
+ </choose>
+ </group>
+ </if>
+ <else-if type="bill">
+ <group delimiter=", ">
+ <group delimiter=" ">
+ <text variable="genre"/>
+ <group delimiter=" ">
+ <choose>
+ <if variable="chapter-number container-title" match="none">
+ <!-- Replace with label variable="number" as that becomes available -->
+ <text term="issue" form="short"/>
+ </if>
+ </choose>
+ <text variable="number"/>
+ </group>
+ </group>
+ <text variable="authority"/>
+ <text variable="chapter-number"/>
+ <group delimiter=" ">
+ <text variable="volume"/>
+ <text variable="container-title"/>
+ <text variable="page-first"/>
+ </group>
+ </group>
+ </else-if>
+ <else-if type="legislation">
+ <choose>
+ <if variable="number">
+ <!--There's a public law number-->
+ <group delimiter=", ">
+ <text variable="number" prefix="Pub. L. No. "/>
+ <group delimiter=" ">
+ <text variable="volume"/>
+ <text variable="container-title"/>
+ <text variable="page-first"/>
+ </group>
+ </group>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <text variable="volume"/>
+ <text variable="container-title"/>
+ <choose>
+ <if variable="section">
+ <group delimiter=" ">
+ <!-- Change to label variable="section" as that becomes available -->
+ <text term="section" form="symbol"/>
+ <text variable="section"/>
+ </group>
+ </if>
+ <else>
+ <text variable="page-first"/>
+ </else>
+ </choose>
+ </group>
+ </else>
+ </choose>
+ </else-if>
+ <else-if type="treaty">
+ <group delimiter=" ">
+ <number variable="volume"/>
+ <text variable="container-title"/>
+ <choose>
+ <if variable="page page-first" match="any">
+ <text variable="page-first"/>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <!-- Replace with label variable="number" if that becomes available -->
+ <text term="issue" form="short" text-case="capitalize-first"/>
+ <text variable="number"/>
+ </group>
+ </else>
+ </choose>
+ </group>
+ </else-if>
+ </choose>
+ </macro>
+ <macro name="citation-locator">
+ <group delimiter=" ">
+ <choose>
+ <if locator="chapter">
+ <label variable="locator" text-case="capitalize-first"/>
+ </if>
+ <else>
+ <label variable="locator" form="short"/>
+ </else>
+ </choose>
+ <text variable="locator"/>
+ </group>
+ </macro>
+ <citation et-al-min="3" et-al-use-first="1" disambiguate-add-year-suffix="true" disambiguate-add-names="true" disambiguate-add-givenname="true" collapse="year" givenname-disambiguation-rule="primary-name-with-initials">
+ <sort>
+ <key macro="author-bib" names-min="3" names-use-first="1"/>
+ <key macro="date-sort-group"/>
+ <key macro="date-sort-date" sort="ascending"/>
+ <key variable="status"/>
+ </sort>
+ <layout prefix="(" suffix=")" delimiter="; ">
+ <group delimiter=", ">
+ <text macro="author-intext"/>
+ <text macro="date-intext"/>
+ <text macro="citation-locator"/>
+ </group>
+ </layout>
+ </citation>
+ <bibliography hanging-indent="true" et-al-min="21" et-al-use-first="19" et-al-use-last="true" entry-spacing="0" line-spacing="2">
+ <sort>
+ <key macro="author-bib"/>
+ <key macro="date-sort-group"/>
+ <key macro="date-sort-date" sort="ascending"/>
+ <key variable="status"/>
+ <key macro="title"/>
+ </sort>
+ <layout>
+ <choose>
+ <if type="bill legal_case legislation treaty" match="any">
+ <!-- Legal items have different orders and delimiters -->
+ <choose>
+ <if variable="DOI URL" match="any">
+ <text macro="legal-cites"/>
+ </if>
+ <else>
+ <text macro="legal-cites" suffix="."/>
+ </else>
+ </choose>
+ </if>
+ <else>
+ <group delimiter=" ">
+ <group delimiter=". " suffix=".">
+ <text macro="author-bib"/>
+ <text macro="date-bib"/>
+ <text macro="title-and-descriptions"/>
+ <text macro="container"/>
+ <text macro="event"/>
+ <text macro="publisher"/>
+ </group>
+ <text macro="access"/>
+ <text macro="publication-history"/>
+ </group>
+ </else>
+ </choose>
+ </layout>
+ </bibliography>
+</style>
diff --git a/biblio.bib b/biblio.bib
new file mode 100644
index 0000000000000000000000000000000000000000..f23db56b9c81bfbf3bf1405b8a96c7280159619e
--- /dev/null
+++ b/biblio.bib
@@ -0,0 +1,150 @@
+@inproceedings{bohbot2018,
+ TITLE = {{Presenting the N{\'e}nufar Project: a Diachronic Digital Edition of the Petit Larousse Illustr{\'e}}},
+ AUTHOR = {Bohbot, Herv{\'e} and Frontini, Francesca and Luxardo, Giancarlo and Khemakhem, Mohamed and Romary, Laurent},
+ URL = {https://hal.archives-ouvertes.fr/hal-01728328},
+ BOOKTITLE = {{GLOBALEX 2018 - Globalex workshop at LREC2018}},
+ ADDRESS = {Miyazaki, Japan},
+ PAGES = {1-6},
+ YEAR = {2018},
+ MONTH = May,
+ KEYWORDS = {Dictionaries ; Petit Larousse ; TEI},
+ PDF = {https://hal.archives-ouvertes.fr/hal-01728328/file/presenting-nenufar-project%20%282%29.pdf},
+ HAL_ID = {hal-01728328},
+ HAL_VERSION = {v1},
+}
+
+@article{jacquet-pfau2015,
+ AUTHOR = {Jacquet-Pfau, C.},
+ JOURNAL = {{\'E}la. {\'E}tudes de linguistique appliqu{\'e}e},
+ PAGES = {85-100},
+ TITLE = {{\'E}laboration et destin{\'e}e d'une encyclop{\'e}die la fin du XIXe si{\`e}cle : les trente-et-un volumes de \textit{La Grande Encyclop{\'e}die}, Inventaire raisonn{\'e} des sciences, des lettres et des arts par une Soci{\'e}t{\'e} de savants et de gens de lett},
+ VOLUME = {177},
+ YEAR = {2015},
+ URL = {https://doi.org/10.3917/ela.177.0085},
+}
+
+@article{roe2016,
+ AUTHOR={Roe, Glenn and Gladstone, Clovis and Morrissey, Robert},
+ TITLE={Discourses and Disciplines in the Enlightenment: Topic Modeling the French Encyclopédie},
+ JOURNAL={Frontiers in Digital Humanities},
+ VOLUME={2},
+ YEAR={2016},
+ URL={https://www.frontiersin.org/article/10.3389/fdigh.2015.00008},
+ DOI={10.3389/fdigh.2015.00008},
+ ISSN={2297-2668},
+ ABSTRACT={This article describes the use of latent Dirichlet allocation (LDA), or topic modeling, to explore the discursive makeup of the eighteenth century Encyclopédie of Denis Diderot and Jean le Rond d’Alembert (1751–1772). Expanding upon previous work modeling the Encyclopédie’s ontology, or classification scheme, we examine the abstractions used by its editors to visualize the various “systems†of knowledge that the work proposes, considered here as heuristic tools for navigating the complex information space of the Encyclopédie. Using these earlier experiments with supervised machine-learning models as a point of reference, we introduce the notion of topic modeling as a “discourse analysis tool†for Enlightenment studies. In so doing, we draw upon the tradition of post-structuralist French discourse analysis, one of the first fields to embrace computational approaches to discursive text analysis. Our particular use of LDA is thus aimed primarily at uncovering interdisciplinary “discourses†in the Encyclopédie that run alongside, under, above, and through the original classifications. By mapping these discourses and discursive practices, we can begin to move beyond the organizational (and physical) limitations of the print edition, suggesting several possible avenues of future research. These experiments thus attest once again to the enduring relevance of the Encyclopédie as an exemplary Enlightenment text. Its rich dialogical structure, whether studied using traditional methods of close reading or through the algorithmic processes described in this article, is perhaps only now coming fully to light thanks to recent developments in digital resources and methods.}
+}
+
+@inproceedings{vigier2019,
+ TITLE = {{GeoDISCO: Encyclopedic Geographical Discourse in France from the
+ Enlightenment to Wikipedia}},
+ AUTHOR = {Vigier, Denis and Moncla, Ludovic and Joliveau, Thierry and
+ McDonough, Katherine and Brenon, Alice},
+ URL = {https://hal.archives-ouvertes.fr/hal-02474835},
+ BOOKTITLE = {{GIR'19, 13th International Workshop on Geographic
+ Information Retrieval}},
+ ADDRESS = {Lyon, France},
+ YEAR = {2019},
+ MONTH = Nov,
+ HAL_ID = {hal-02474835},
+ HAL_VERSION = {v1},
+}
+
+@article{williams2017,
+ TITLE = {{MAPPING A DICTIONARY Using Atlas ti and XML to analyse a late
+ XVII th century dictionary}},
+ AUTHOR = {Williams, Geoffrey},
+ URL = {https://halshs.archives-ouvertes.fr/halshs-01612601},
+ JOURNAL = {{RiCognizioni}},
+ PUBLISHER = {{Universit{\`a} degli Studi di Torino}},
+ VOLUME = {7},
+ NUMBER = {4},
+ PAGES = {161-180},
+ YEAR = {2017},
+ DOI = {10.13135/2384-8987/2104},
+ KEYWORDS = {CAQDAS ; TEI ; Dictionary ; Atlas it},
+ PDF = {https://halshs.archives-ouvertes.fr/halshs-01612601/file/Itinerari_Williams.pdf},
+ HAL_ID = {halshs-01612601},
+ HAL_VERSION = {v1},
+}
+
+@article{blanchard2002,
+ TITLE = {{Le syst{\`e}me de renvois dans l'Encyclop{\'e}die : Une
+ cartographie des structures de connaissances au XVIIIe si{\`e}cle}},
+ AUTHOR = {Blanchard, G. and Olsen, Mark},
+ URL = {https://hal.archives-ouvertes.fr/hal-03336269},
+ JOURNAL = {{Recherches sur Diderot et sur l'Encyclop{\'e}die}},
+ PUBLISHER = {{Soci{\'e}t{\'e} Diderot}},
+ SERIES = {L'Encyclop{\'e}die en ses nouveaux atours
+ {\'e}lectroniques: vices et vertus du virtuel},
+ NUMBER = {31-32},
+ PAGES = {45},
+ YEAR = {2002},
+ DOI = {10.4000/rde.122},
+ PDF = {https://hal.archives-ouvertes.fr/hal-03336269/file/rde-122.pdf},
+ HAL_ID = {hal-03336269},
+ HAL_VERSION = {v1},
+}
+
+@article{lojkine2013,
+ TITLE = {{`` Et l'auteur anonyme n'est pas un l{\^a}che {\ldots} '' Diderot, l'engagement sans le nom}},
+ AUTHOR = {Lojkine, St{\'e}phane},
+ URL = {https://hal.archives-ouvertes.fr/hal-01081454},
+ JOURNAL = {{Litt{\'e}ratures classiques}},
+ PUBLISHER = {{Soci{\'e}t{\'e} de litt{\'e}ratures classiques (SLC) / diff{\'e}rents {\'e}diteurs}},
+ SERIES = {L'anonymat de l'{\oe}uvre (XVIe-XVIIIe si{\`e}cles)},
+ VOLUME = {2013/1},
+ NUMBER = {80},
+ PAGES = {249-263},
+ YEAR = {2013},
+ KEYWORDS = {Diderot ; Encyclop{\'e}die ; engagement ; anonymat},
+ PDF = {https://hal.archives-ouvertes.fr/hal-01081454/file/Diderot_Anonymat_article.pdf},
+ HAL_ID = {hal-01081454},
+ HAL_VERSION = {v1},
+}
+
+@book{moureau2001,
+ TITLE = {{Le Roman vrai de l’Encyclopédie}},
+ AUTHOR = {Moureau, François},
+ YEAR = {2001},
+ PUBLISHER = {Gallimard},
+ ADDRESS = {Paris},
+ URL = {https://catalogue.bnf.fr/ark:/12148/cb36204966x},
+ PAGES = {124-129},
+}
+
+@inproceedings{heiden2010,
+ TITLE = {{The TXM Platform : Building Open-Source Textual Analysis
+ Software Compatible with the TEI Encoding Scheme}},
+ AUTHOR = {Heiden, Serge},
+ URL = {https://halshs.archives-ouvertes.fr/halshs-00549764},
+ BOOKTITLE = {{24th Pacific Asia Conference on Language, Information
+ and Computation}},
+ ADDRESS = {Sendai, Japan},
+ EDITOR = {R. Otoguro and K. Yoshimoto and K. Ishikawa and H.
+ Umemoto and \& Y. Harada},
+ PUBLISHER = {{Institute for Digital Enhancement of Cognitive
+ Development, Waseda University}},
+ VOLUME = {2},
+ NUMBER = {3},
+ PAGES = {389‑398},
+ YEAR = {2010},
+ MONTH = Nov,
+ KEYWORDS = {textometry ; open-source ; search
+ engine ; statistical analysis ; xml-tei
+ corpora},
+ PDF = {https://halshs.archives-ouvertes.fr/halshs-00549764/file/paclic24_sheiden.pdf},
+ HAL_ID = {halshs-00549764},
+ HAL_VERSION = {v1},
+}
+
+@article{dijkstra59,
+ AUTHOR = "Edsger. W. Dijkstra",
+ TITLE = "A note on two problems in connexion with graphs.",
+ YEAR = "1959",
+ JOURNAL = "Numerische Mathematik",
+ VOLUME = 1,
+ PAGES = {269--271},
+ URL = "http://gdzdoc.sub.uni-goettingen.de/sub/digbib/loader?did=D196313",
+ filesize = {256 KB},
+}
diff --git a/feedback.txt b/feedback.txt
new file mode 100644
index 0000000000000000000000000000000000000000..fb7ea3b7f6106562f4e8bc474d5ff10967171e67
--- /dev/null
+++ b/feedback.txt
@@ -0,0 +1,46 @@
+The specificities of encoding encyclopedias: towards a new standard?
+
+Spelling
+oConsistently use British English spelling.
+
+Title
+oDo not capitalize important words in title, except for proper names or when it is generally required.
+oProvide academic affiliation under the name of author(s).
+oAvoid e-mail address here.
+oDelete topic and keywords, as they are not required at this stage.
+
+General remarks
+oConsistently call your work ‘this chapter’.
+oNumber sections with one digit (1., 2., etc.), and subsections with two digits (1.1, 1.2, etc.). Do not use sub-sub sections (2.1.1, 2.1.2, etc.). Do not use sub-sub-sub sections (2.1.1.1, 2.1.1.2, etc.).
+?Use bold face for sections and subsections. Do not indent.
+oRevise section numbering to avoid empty sub-sections, such as 2.1.
+oDo not use bulleted lists. Write a paragraph instead.
+oUse 1cm indentation for the first line in all paragraphs except the first line of the (sub)section.
+!Revise the text. Avoid gaps and repetitions like “to future other scientific projectsâ€.
+
+Abstract
+oThe abstract must include the aim of the research, a brief description of the method and an overview of the conclusions.
+oAvoid references in abstract.
+oAvoid abstract notes. Include full name of projects and cite them in the Reference section if necessary.
+
+Body
+oExplain how your aims are relevant for and contribute to the topic of the first part of the book: Lexical databases and language processing in digital historical lexicography.
+oExplain clearly in what respect your method departs from previous approaches and improves them.
+oIt would be of help that a brief introduction to each section gave an overview of the contents of the following sub-sections.
+oNumber figures. Refer to them in text as Figure 1, Figure 2, etc. Describe briefly the figures by explicitly referring to the number of the figure in question.
+oExtract must be considered figures.
+oAttributes like [cid:image001.png@01D86623.7C6238D0] must be considered figures.
+oUse figure captions consistently.
+
+Format
+-Avoid double blank spaces and revise punctuation.
+-Avoid double blank lines between paragraphs.
+?Do not place notes under the tables. Use footnotes.
+oJustify the text both on the left and the right.
+
+References
+oDo not present references as bulleted paragraphs.
+oCheck the reference list.
+oSort the reference list alphabetically, by author’s surname.
+
+oIf the research has been funded through a grant, insert an Acknowledgement section before the references.
diff --git a/manifest.scm b/manifest.scm
index 950bbdfadf85e9b14c8e4df8f0257dd1c7affec2..d0971bcf0cd0f3d6d620ac0ab02d155b122d0dbb 100644
--- a/manifest.scm
+++ b/manifest.scm
@@ -5,5 +5,7 @@
(gnu packages pdf)
(gnu packages tex))
-(packages->manifest
- (list gnu-make graphviz pandoc poppler texlive))
+(let
+ ((pandoc-fignos (load "pandoc-fignos.scm")))
+ (packages->manifest
+ (list gnu-make graphviz pandoc poppler texlive pandoc-fignos)))
diff --git a/pandoc-fignos.scm b/pandoc-fignos.scm
new file mode 100644
index 0000000000000000000000000000000000000000..a79ddaede387dc791565018359c41ea29c891c6f
--- /dev/null
+++ b/pandoc-fignos.scm
@@ -0,0 +1,24 @@
+(use-modules ((gnu packages python-xyz) #:select (python-psutil))
+ ((gnu packages textutils) #:select (python-pandocfilters))
+ (guix build-system python)
+ ((guix download) #:select (url-fetch))
+ ((guix licenses) #:select (gpl3))
+ (guix packages))
+
+(let
+ ((python-pandoc-xnos (load "pandoc-xnos.scm")))
+ (package
+ (name "python-pandoc-fignos")
+ (version "2.4.0")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (pypi-uri "pandoc-fignos" version))
+ (sha256
+ (base32 "0jc8glwkhwxi4qc3jh1ssgvrw2jhf9gxv470kwp42948wkmfsn3h"))))
+ (build-system python-build-system)
+ (propagated-inputs (list python-pandoc-xnos))
+ (home-page "https://github.com/tomduck/pandoc-fignos")
+ (synopsis "Figure number filter for pandoc")
+ (description "Figure number filter for pandoc")
+ (license gpl3)))
diff --git a/pandoc-xnos.scm b/pandoc-xnos.scm
new file mode 100644
index 0000000000000000000000000000000000000000..8d1eed1449273827f2f9ec830afbc16db300f665
--- /dev/null
+++ b/pandoc-xnos.scm
@@ -0,0 +1,34 @@
+(use-modules ((gnu packages python-xyz) #:select (python-psutil python-tox))
+ ((gnu packages textutils) #:select (python-pandocfilters))
+ (guix build-system python)
+ ((guix download) #:select (url-fetch))
+ ((guix licenses) #:select (gpl3))
+ (guix packages))
+
+(package
+ (name "python-pandoc-xnos")
+ (version "2.5.0")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (pypi-uri "pandoc-xnos" version))
+ (sha256
+ (base32 "1bjhwbfz67fm8ckvhhadi7y82cnlv2mnarfwfg2wwklyi667663w"))))
+ (build-system python-build-system)
+ ;(native-inputs (list pandoc python-tox))
+ (arguments
+ `(#:tests? #f
+ #:phases
+ (modify-phases %standard-phases
+ (replace 'check
+ (lambda* (#:key tests? #:allow-other-keys)
+ (if tests?
+ (begin
+ (invoke "ls")
+ (invoke "pwd")
+ (invoke "./test/test.py"))))))))
+ (propagated-inputs (list python-pandocfilters python-psutil))
+ (home-page "https://github.com/tomduck/pandoc-xnos")
+ (synopsis "Library code for the pandoc-xnos filter suite.")
+ (description "Library code for the pandoc-xnos filter suite.")
+ (license gpl3))
diff --git a/snippets/gelocus.md b/snippets/gelocus.md
index ffe4ab7231fe18152ed9677fb5e116d9c1bca248..f320bedc4b27c75ea0be5f760df2b28aa5980c9b 100644
--- a/snippets/gelocus.md
+++ b/snippets/gelocus.md
@@ -4,7 +4,7 @@ header-includes:
\usepackage{graphicx}
\usepackage[left=0cm,top=0cm,right=0cm,nohead,nofoot]{geometry}
\geometry{
- paperwidth=9.1cm,
+ paperwidth=9.2cm,
paperheight=1.8cm,
margin=0cm
}
@@ -12,7 +12,7 @@ header-includes:
```xml
<p>
- (V. <ref target="boeuf-0">Boeuf</ref> et
- <ref target="chevrotain-0">Chevrotain</ref>).
+ (V. <ref target="#boeuf-0">Boeuf</ref> et
+ <ref target="#chevrotain-0">Chevrotain</ref>).
</p>
```