All translations1 are maintained via GNUN (see http://www.gnu.org/software/gnun/), which significantly eases maintenance and avoids the unpleasant situation where a translation is lagging behind the original. See Advantages in The GNUnited Nations Manual.
Since September 2008 all new translations at gnu.org are installed in .po format, and the .html is generated automatically. Here are the steps to produce and submit such a translation:
cvs -z3 -d:pserver:firstname.lastname@example.org:/web/www co www/gnu
This command will fetch only the /gnu directory—in other words, all articles at http://gnu.org/gnu.
You can also fetch single files by their respective URLs. For example, the URL for the template file of http://www.gnu.org/philosophy/free-sw.html is http://www.gnu.org/philosophy/po/free-sw.pot; the URL for its lang PO file (when available) is always http://www.gnu.org/philosophy/po/free-sw.lang.po:
TEMPLATE_LINGUASvariable at server/gnun/gnun.mk, then you don’t have to do anything. If it is not, the required files are defined via the
extra-templatesvariable in server/gnun/gnun.mk—you can translate and submit them in the usual way, together with the translation of the essay.
If you don’t want to translate the templates for whatever reason—do not worry, the web-translators will install empty templates (which means the English strings will be used).
It is quite possible that there will be errors or typos, so once you are
informed that the translation is online, check it carefully and if
necessary, resubmit the PO file with corrections. Do not forget to run
cvs update first and edit the updated .po file from the
repository—most probably the Translation Managers have already made
some modifications to it, usually to fix validation errors and to
complete the PO file header.
Well—not really, but the goal is to maintain all of them.