From cec9d5255b316022f1062e512b59ecb0c3e7e22d Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Sep 13 2011 04:33:12 +0000 Subject: Update `Manuals/Texinfo/localizing.docbook'. --- diff --git a/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook b/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook index 0817027..263e10b 100644 --- a/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook +++ b/Manuals/Tcar-ug/Manuals/Texinfo/localizing.docbook @@ -1,21 +1,21 @@ - Texinfo Document Localization + Texinfo Document Internationalization - The localization of documentation manuals produced through - texinfo documentation backend takes place by creating one - documentation manual for each language individually. 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 internationalization of documentation manuals produced + through texinfo documentation backend takes place by creating + one documentation manual for each language individually. + Documentation manuals created in this configuration 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 (the source manual) and + produce several translated manuals based on its content. To + keep track of changes inside the source manual, the + underlayout version control system must be used. Notice that + there is no direct way to apply + gettext The gettext program translates a natural language message into the user's language, by @@ -23,44 +23,76 @@ information about the gettext program, run info gettext. - procedures cannot be applied to texinfo source - files. A possible work around would be to convert each - 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. + procedures to texinfo source files. + + + + In order to maintain localization of texinfo source files + through gettext procedures, it is + necessary to convert the texinfo source files into XML format. + This way it would be possible to make use of the + locale and render + functionalities of centos-art.sh script to + maintain translation messages in different languages through + portable objets and producing localized XML files based on + such portable objects, respectively. Once the localized XML + files are available, it would be matter of using an XSLT + processor (e.g., xsltproc) to realize the + convertion from XML to texinfo format. Nevertheless, this + workaround fails because the texinfo Document Type Definition + (DTD) required for validation and the related XSLT files + required for transformation itself are not available + inside &TCD; (release 5.5). + + Another similar approch to maintain localization of texinfo + source files through gettext + procedures would be to convert texinfo source file to DocBook + format, to whom there are DTD files available inside &TCD;. + This way it would be possible to make use of the + locale and render + functionalities of centos-art.sh script. + Nevertheless, this workaround seems fails when the DocBook + output is produced from makeinfo command + (as in texinfo-4.8-14.el5). It doesn't + produce a valid DocBook document, according to DocBook DTDs + available inside &TCD; (release 5.5) so, transformation of + such file isn't possible either. + + + + The only visible way to localize texinfo source files, at this + moment, is to create one documentation manual for each + language we want to support documentation for. + + Texinfo Document Language - The language information of documentation manuals produced - through texinfo documentation backend is declared by texinfo's - @documentlanguage command and can take any - language code from ISO-639 as argument. 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. + The language information of those documentation manuals + produced through texinfo documentation backend is declared by + texinfo's @documentlanguage command. This + command receives one argument refering the language code (as + in ISO-639 standard) and must be set inside the manual's main + definition file. Generally, there is no need to change the + document language declaration once it has been created by the + help functionality of + centos-art.sh script; unless you + mistakently create the manual for a locale code different to + that one you previously pretended to do in first place, of + course. - 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 its 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 + The language information used in both the texinfo source files + and the XHTML output produced when they are rendered through + the help functionality of + centos-art.sh script is determined by the + user's session LANG environment variable. This + variable 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.