Next: , Previous: Invoking GNUN, Up: Usage


2.2 Defining Articles to be Built

The file gnun.mk contains variable definitions, based on which almost all other important variables are computed. In other words, the variables defined in that file directly affect the overall behavior of the build process.

There are two types of variables, which are specifically separated in order to make translators' life easier: variables that translators are free to modify and variables that are modified by the web-translators staff1, ideally after performing some local tests. A translation team leader should update only TEMPLATE_LINGUAS and HOME_LINGUAS; everything else is supposed to be built automagically, without manual intervention. If not, that is a bug that should be reported and fixed.

TEMPLATE_LINGUAS
A space-separated list with languages. Add here your language code if and only if you have all the SSI templates translated, and have already committed in the repository all these template files: server/po/head-include-1.lang.po, server/po/body-include-1.lang.po, server/po/body-include-2.lang.po, server/po/footer-text.lang.po, as well as the templates that are not under GNUN's control and are translated manually, like server/header.lang.html, server/banner.lang.html and server/footer.lang.html.


HOME_LINGUAS
Add your language code if you have already committed po/home.lang.po, that way the homepage for your language will be built. It is not acceptable to have your language code defined in this variable, but not in TEMPLATE_LINGUAS.


ROOT
Add here articles that are in the server root, like keepingup.html and provide.html. Always write only the basename of the article, i.e. if you add these two articles, the value of ROOT should be keepingup provide. This is true for all the variables that expect values in the form of article names.


ALL_DIRS
The list of directories containing articles, like philosophy, gnu, licenses, etc.


gnu
philosophy
...directory...
A space-separated list of basenames for articles residing in directory, for which POTs will be generated and updated when the original article changes. If an article is missing here, there is no way its translations to be maintained via GNUN.

Footnotes

[1] Only because presumably, they are more familiar with GNUnited Nations' internals. From a purely technical point of view, there is no difference.