diff --git a/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook b/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook index 6014c4f..6281e52 100644 --- a/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook +++ b/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook @@ -5,59 +5,86 @@ The localization of documentation manuals produced through texinfo documentation backend takes place by creating one - documentation manual for each language. These manuals don't - have a direct relation among themselves except that one - adopted by people writting them in order to keep their content - syncronized one another. This configuration needs to - predefine a source documentation manual and translated - versions which derivate from it so as to keep the localization - work organized. To keep track of changes, the underlaying - version control system must be used. Notice that most of these - limitations might be reduced if it would be possible to apply - gettext procedures to texinfo - source files. + documentation manual for each supported language. These + manuals don't have a direct relation among themselves except + that one adopted by people writting them in order to keep + their content syncronized. In this configuration translators + take one documentation manual as reference and produce + translated versions of it. To keep track of changes, the + underlaying version control system must be used. + + + + Notice that gettext + + The gettext program translates + a natural language message into the user's language, by + looking up the translation in a message catalog. For more + information about gettext + program run info gettext. + + procedures cannot be applied to texinfo source + files. A possible work around would be to convert the + documentation manual from texinfo format to XML format and + then apply gettext procedures on it + through xml2po command. This would produce + a translated XML file which can be used to convert back the + documentation manual to texinfo format so it can be exported + to convenctional output formats. Even though it is possible to + convert texinfo source files into XML, the DTD and XSLT files + required to realize both markup validation and transnformation + back into texinfo format (or possibly other formats) are not + available inside &TCD; release 5.5. Texinfo Document Language - To create a documentation manual in English language the - LANG environment variable must be set to - en_US.UTF-8 or something similar. Likewise, if - you want to create documentation manuals in a language other - than English, be sure the LANG environment - variable is set to the appropriate locale code. Generally, - you can customize the user's session locale information - in the graphical login screen before login, or once you've - login by explicitly setting the value of LANG - environment variable inside the - ~/.bash_profile file. To see the list of - all the locales supported, you can use the - locale -a | less command. + The language information of documentation manuals produced + through texinfo documentation backend is defined by texinfo's + @documentlanguage command. This command is set in + the manual's main definition file and, generally, there is no + need to change it unless you mistakently create the manual for + a locale code different to that one you previously pretended + to do in first place. - Inside the main definition file of each documentation manual, - the language information is set by texinfo's - @documentlanguage command, when the documentation - manual is created through the help functionality - of centos-art.sh script. Generally, there - is no need to change the language information set by - @documentlanguage command once the document has - been created, unless you mistakently create the manual for a - locale code different to that one you previously pretended in - first place. + The user's session locale information, as set in + LANG environment variable, determines the + language information used by new documentation manuals created + through the help functionality of + centos-art.sh script and the XHTML output + produced from texi2html command. The + user's session locale information can be customized in the + graphical login screen before login, or once you've login by + explicitly setting the value of LANG + environment variable inside the + ~/.bash_profile file. + + + To create documentation manuals in English language the + LANG environment variable must be set to + en_US.UTF-8 or something similar. Likewise, if + you want to create documentation manuals in a language other + than English, be sure the LANG environment + variable is set to the appropriate locale code, based on the + output of locale -a | less command. + + + - When producing output, the language information set by - @documentlanguage texinfo command is ignore in - Info and HTML output produced by makeinfo - command in the texinfo-4.8-14.el5 package, - but cosidered by Tex program to redefine various English words - used in the output (e.g., Chapter, - Index, See, and so on) based on - the current language set in. + When producing output from texinfo source files, the language + information set by @documentlanguage texinfo + command is ignored in Info and HTML output produced by + makeinfo command in the + texinfo-4.8-14.el5 package, but cosidered + by Tex program to redefine various English words used in the + output (e.g., Chapter, Index, + See, and so on) based on the current language + set in.