Mapping language processing

This page follows the model of Mapping ODD Processing in trying to provide a clear general introduction to the way that different language inputs are processed in the building of Guidelines/documentation.

TEI Guidelines

This section deals with the Guidelines build process specifically.

Input parameters

The Guidelines Makefile provides the following set of parameters related to language processing when building the Guidlines:

- ALLLANGUAGES=en
- LANGUAGE=en
- INPUTLANGUAGE=en
- DOCUMENTATIONLANGUAGE=en

ALLLANGUAGES is a parameter which can take multiple values, space-separated; for each of those values, a separate version of the Guidelines will be built in its own folder by using the ant macro buildweb. This calls the Stylesheets utilties/Guidelines.xsl, passing the current value of the language in all three of the following parameters:

- lang
- doclang
- documentationLanguage

(These will be documented later.) This parameter is automatically set to the following list of languages for a number of Makefile targets, including teiwebsiteguidelines.

LANGUAGE is an apparently unused parameter; it appears in both the P5/Makefile and the P5/Test/Makefile, but is never used in either. *We recommend deleting this confusing parameter.*

INPUTLANGUAGE governs which source tree for the Guidelines specifically is used; it governs the name of the source file,[^1] setting the variable DRIVER to this file. That makes the root language effectively the input language, and then when other language versions are built in the html-web.stamp target, they are based on the input language rather than the default (en), assuming they are different.

[^1]:P5/Source/en/Guidelines-en.xml or P5/Source/fr/Guidelines-fr.xml are the only two available right now, and the French chapter points only to English source files anyway, because the French header chapter is out of date and will not build