Mapping language processing: Difference between revisions
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
- INPUTLANGUAGE=en | - INPUTLANGUAGE=en | ||
- DOCUMENTATIONLANGUAGE=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 <code>buildweb</code>. This calls the Stylesheets <code>utilties/Guidelines.xsl</code>, passing the current value of the language in all three of the following parameters: | |||
- lang | |||
- doclang | |||
- documenationLanguage | |||
(These will be documented later.) | |||
Revision as of 16:36, 6 November 2020
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 - documenationLanguage
(These will be documented later.)