A.1 Translating strings

A.1.1 Contributing to existing translations

If the language is allready supported, then there will be a file in the ‘i18n’ directory with name the two-letter ISO-639 language code. In that case you can enhance the translations by editing this file. There is a $LANGUAGES->{'language'} hash in that file. The keys are the english strings, in '', the values (in '' after =>) are the translations. When a string contains a ‘%’ followed by ‘{’ name ‘}’ it means that the string will be expanded by texi2html. For an example, see Customizing strings written by texi2html.

After that you should run the command ./manage_i18n.pl merge in the top directory, it should merge your file with the existing files in ‘translations.pl’, which is incorporated to the ‘texi2html’ script by make.

A.1.2 Contributing translations to another language

If the language isn't currently supported, copy the ‘en’ file in ‘i18n’ to a file with name the two-letter ISO-639 language code of your language and then add your translations to the strings. You could also add your two-letter language code in the ‘manage_i18n.pl’ file in the @known_languages array.

After that you should run the command ./manage_i18n.pl update lang and ./manage_i18n.pl merge in the top directory.

Obsoleted strings are not removed from the files, they are still present in the $T2H_OBSOLETE_STRINGS->{'language'} hash in case the string is reused later.

If you made change to strings specified in installed files (see section Installation of texi2html) you will have to reinstall them otherwise the installated files will take precedence (see section Use initialization files for fine tuning).

Doku-Base