diff --git a/Identity/Manual/Directories/chapter-menu.texi b/Identity/Manual/Directories/chapter-menu.texi index 14180cf..a678d0f 100644 --- a/Identity/Manual/Directories/chapter-menu.texi +++ b/Identity/Manual/Directories/chapter-menu.texi @@ -5,7 +5,6 @@ * Directories trunk Identity:: * Directories trunk Identity Brands:: * Directories trunk Identity Fonts:: -* Directories trunk Identity Locales:: * Directories trunk Identity Manual:: * Directories trunk Identity Palettes:: * Directories trunk Identity Themes:: @@ -29,6 +28,7 @@ * Directories trunk Identity Themes Motifs Pipes:: * Directories trunk Identity Themes Motifs TreeFlower:: * Directories trunk Identity Webenv:: +* Directories trunk Locales:: * Directories trunk Scripts:: * Directories trunk Scripts Functions:: * Directories trunk Scripts Functions Help:: diff --git a/Identity/Manual/Directories/chapter-nodes.texi b/Identity/Manual/Directories/chapter-nodes.texi index be91133..76118fd 100644 --- a/Identity/Manual/Directories/chapter-nodes.texi +++ b/Identity/Manual/Directories/chapter-nodes.texi @@ -28,11 +28,6 @@ @cindex Directories trunk Identity Fonts @include Directories/trunk/Identity/Fonts.texi -@node Directories trunk Identity Locales -@section The @file{trunk/Identity/Locales} Directory -@cindex Directories trunk Identity Locales -@include Directories/trunk/Identity/Locales.texi - @node Directories trunk Identity Manual @section The @file{trunk/Identity/Manual} Directory @cindex Directories trunk Identity Manual @@ -148,6 +143,11 @@ @cindex Directories trunk Identity Webenv @include Directories/trunk/Identity/Webenv.texi +@node Directories trunk Locales +@section The @file{trunk/Locales} Directory +@cindex Directories trunk Locales +@include Directories/trunk/Locales.texi + @node Directories trunk Scripts @section The @file{trunk/Scripts} Directory @cindex Directories trunk Scripts diff --git a/Identity/Manual/Directories/trunk/Identity.texi b/Identity/Manual/Directories/trunk/Identity.texi index 19e8006..0f723bb 100644 --- a/Identity/Manual/Directories/trunk/Identity.texi +++ b/Identity/Manual/Directories/trunk/Identity.texi @@ -80,7 +80,7 @@ is perfect to consolidate @emph{The CentOS Translation SIG}. If you love translating, you'll find lot of messages waiting for you to translate here. -@xref{Directories trunk Identity Locales}, for more information. +@xref{Directories trunk Locales}, for more information. @end table @subsubsection Corporate Communication diff --git a/Identity/Manual/Directories/trunk/Identity/Locales.texi b/Identity/Manual/Directories/trunk/Identity/Locales.texi deleted file mode 100644 index 7e5457c..0000000 --- a/Identity/Manual/Directories/trunk/Identity/Locales.texi +++ /dev/null @@ -1,56 +0,0 @@ -The @file{trunk/Locales} directory exists to store the translation -messages used to produce content in different languages. - -Translation messages are organized using the directory structure of -the component being translated. For example, if we want to provide -translation messages for @file{trunk/Manuals/Repository}, then the -@file{trunk/Locales/Manuals/Repository} directory needs to be created. - -Once the locale directory exists for the component we want to provide -translation messages for, it is necessary to create the translation -files where translation messages are. The translation files follows -the concepts of @command{xml2po} and GNU @command{gettext} tools. - -The basic translation process is as follow: first, translatable -strings are extracted from files and a portable object template (.pot) -is created or updated with the information. Using the portable object -template, a portable object (.po) is created or updated for translator -to locale the messages retrived. Finally, a machine object (.mo) is -created from portable object to sotore the translated messages. - -Inside the repository there are two ways to retrive translatable -strings from files. The first one is through @command{xml2po} command -and the second through @command{xgettext} command. The @command{xml2po} -is used to retrive translatable strings from XML files (e.g., Scalable -Vector Graphics, DocBook, etc.) and the @command{xgettext} command is -used to retrive translatable strings from shell scripts files (e.g., -the files that make the @command{centos-art.sh} command-line -interface). - -When translatable strings are retrived from XML files, using the -@command{xml2po} command, there is no need to create the machine -object as we do when translatable strings ar retrived from shell -files, using the @command{xgettext} command. The @command{xml2po} -produces a temporal machine object in order to create a translated XML -file. Once the translated XML file has been created the machine object -is no longer needed. On the other hand, the machine object produced by -the @command{xgettext} command is required by the system in order for -the show shell script localized messages. - -Another difference between @command{xml2po} and @command{xgettext} we -need to be aware of is the directory structure used to store machine -objects. In @command{xml2po}, the machine object is created in the -current working directory as @file{.xml2po.mo} and can be safetly -removed once the translated XML file has been created. In the case of -@command{xgettext}, the machine object needs to be stored in the -@file{$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo} file in order -for the system to interpret it and should not be removed since it is -the file that contain the translation messages themselves. - -Automation of localization tasks is achived through the @code{locale} -functionality of command-line interface. - -@menu -* Directories trunk Scripts Functions Locale:: -@end menu - diff --git a/Identity/Manual/Directories/trunk/Locales.texi b/Identity/Manual/Directories/trunk/Locales.texi new file mode 100644 index 0000000..7e5457c --- /dev/null +++ b/Identity/Manual/Directories/trunk/Locales.texi @@ -0,0 +1,56 @@ +The @file{trunk/Locales} directory exists to store the translation +messages used to produce content in different languages. + +Translation messages are organized using the directory structure of +the component being translated. For example, if we want to provide +translation messages for @file{trunk/Manuals/Repository}, then the +@file{trunk/Locales/Manuals/Repository} directory needs to be created. + +Once the locale directory exists for the component we want to provide +translation messages for, it is necessary to create the translation +files where translation messages are. The translation files follows +the concepts of @command{xml2po} and GNU @command{gettext} tools. + +The basic translation process is as follow: first, translatable +strings are extracted from files and a portable object template (.pot) +is created or updated with the information. Using the portable object +template, a portable object (.po) is created or updated for translator +to locale the messages retrived. Finally, a machine object (.mo) is +created from portable object to sotore the translated messages. + +Inside the repository there are two ways to retrive translatable +strings from files. The first one is through @command{xml2po} command +and the second through @command{xgettext} command. The @command{xml2po} +is used to retrive translatable strings from XML files (e.g., Scalable +Vector Graphics, DocBook, etc.) and the @command{xgettext} command is +used to retrive translatable strings from shell scripts files (e.g., +the files that make the @command{centos-art.sh} command-line +interface). + +When translatable strings are retrived from XML files, using the +@command{xml2po} command, there is no need to create the machine +object as we do when translatable strings ar retrived from shell +files, using the @command{xgettext} command. The @command{xml2po} +produces a temporal machine object in order to create a translated XML +file. Once the translated XML file has been created the machine object +is no longer needed. On the other hand, the machine object produced by +the @command{xgettext} command is required by the system in order for +the show shell script localized messages. + +Another difference between @command{xml2po} and @command{xgettext} we +need to be aware of is the directory structure used to store machine +objects. In @command{xml2po}, the machine object is created in the +current working directory as @file{.xml2po.mo} and can be safetly +removed once the translated XML file has been created. In the case of +@command{xgettext}, the machine object needs to be stored in the +@file{$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo} file in order +for the system to interpret it and should not be removed since it is +the file that contain the translation messages themselves. + +Automation of localization tasks is achived through the @code{locale} +functionality of command-line interface. + +@menu +* Directories trunk Scripts Functions Locale:: +@end menu +