Blame Manuals/Filesystem/filesystem-html/filesystem_37.html

ee1f37
ee1f37
<html>
ee1f37
ee1f37
ee1f37
Permission is granted to copy, distribute and/or modify this document
ee1f37
under the terms of the GNU Free Documentation License, Version 1.2 or
ee1f37
any later version published by the Free Software Foundation; with no
ee1f37
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
ee1f37
copy of the license is included in the section entitled GNU Free
ee1f37
Documentation License.  
ee1f37
-->
010b2d
ee1f37
ee1f37
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
ee1f37
            Karl Berry  <karl@freefriends.org>
ee1f37
            Olaf Bachmann <obachman@mathematik.uni-kl.de>
ee1f37
            and many others.
ee1f37
Maintained by: Many creative people <dev@texi2html.cvshome.org>
ee1f37
Send bugs and suggestions to <users@texi2html.cvshome.org>
ee1f37
ee1f37
-->
ee1f37
<head>
d05905
<title>CentOS Artwork Repository - Filesystem: 3.34 trunk/Locales</title>
ee1f37
d05905
<meta name="description" content="CentOS Artwork Repository - Filesystem: 3.34 trunk/Locales">
d05905
<meta name="keywords" content="CentOS Artwork Repository - Filesystem: 3.34 trunk/Locales">
ee1f37
<meta name="resource-type" content="document">
ee1f37
<meta name="distribution" content="global">
ee1f37
<meta name="Generator" content="texi2html 1.76">
ee1f37
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
ee1f37
<style type="text/css">
ee1f37
ee1f37
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
ee1f37
ee1f37
a.summary-letter {text-decoration: none}
ee1f37
pre.display {font-family: serif}
ee1f37
pre.format {font-family: serif}
ee1f37
pre.menu-comment {font-family: serif}
ee1f37
pre.menu-preformatted {font-family: serif}
ee1f37
pre.smalldisplay {font-family: serif; font-size: smaller}
ee1f37
pre.smallexample {font-size: smaller}
ee1f37
pre.smallformat {font-family: serif; font-size: smaller}
ee1f37
pre.smalllisp {font-size: smaller}
ee1f37
span.sansserif {font-family:sans-serif; font-weight:normal;}
ee1f37
ul.toc {list-style: none}
ee1f37
-->
ee1f37
</style>
ee1f37
ee1f37
ee1f37
</head>
ee1f37
ee1f37
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
ee1f37
ee1f37
db14a4
[ < ]
010b2d
[ > ]
ee1f37
   
db14a4
[ << ]
db14a4
[ Up ]
193ea4
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
db14a4
[Top]
db14a4
[Contents]
193ea4
[Index]
db14a4
[ ? ]
ee1f37
ee1f37
ee1f37
ee1f37

3.34 trunk/Locales

ee1f37
010b2d

The <tt>`trunk/Locales'</tt> directory exists to store the translation

010b2d
messages used to produce content in different languages.
010b2d

010b2d

Translation messages are organized using the directory structure of

010b2d
the component being translated. For example, if we want to provide
010b2d
translation messages for <tt>`trunk/Manuals/Filesystem'</tt>, then the
010b2d
<tt>`trunk/Locales/Manuals/Filesystem'</tt> directory needs to be created.
010b2d

010b2d

Once the locale directory exists for the component we want to provide

010b2d
translation messages for, it is necessary to create the translation
010b2d
files where translation messages are. The translation files follows
010b2d
the concepts of xml2po and GNU gettext tools.
010b2d

010b2d

The basic translation process is as follow: first, translatable

010b2d
strings are extracted from files and a portable object template (.pot)
010b2d
is created or updated with the information. Using the portable object
010b2d
template, a portable object (.po) is created or updated for translator
010b2d
to locale the messages retrived.  Finally, a machine object (.mo) is
010b2d
created from portable object to sotore the translated messages.
010b2d

010b2d

Inside the repository there are two ways to retrive translatable

010b2d
strings from files. The first one is through xml2po command
010b2d
and the second through xgettext command. The xml2po
010b2d
is used to retrive translatable strings from XML files (e.g., Scalable
010b2d
Vector Graphics, DocBook, etc.) and the xgettext command is
010b2d
used to retrive translatable strings from shell scripts files (e.g.,
010b2d
the files that make the centos-art.sh command-line
010b2d
interface).
010b2d

010b2d

When translatable strings are retrived from XML files, using the

010b2d
xml2po command, there is no need to create the machine
010b2d
object as we do when translatable strings ar retrived from shell
010b2d
files, using the xgettext command. The xml2po
010b2d
produces a temporal machine object in order to create a translated XML
010b2d
file. Once the translated XML file has been created the machine object
010b2d
is no longer needed. On the other hand, the machine object produced by
010b2d
the xgettext command is required by the system in order for
010b2d
the show shell script localized messages.
010b2d

010b2d

Another difference between xml2po and xgettext we

010b2d
need to be aware of is the directory structure used to store machine
010b2d
objects. In xml2po, the machine object is created in the
010b2d
current working directory as <tt>`.xml2po.mo'</tt> and can be safetly
010b2d
removed once the translated XML file has been created. In the case of
010b2d
xgettext, the machine object needs to be stored in the
010b2d
<tt>`$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo'</tt> file in order
010b2d
for the system to interpret it and should not be removed since it is
010b2d
the file that contain the translation messages themselves.
010b2d

68cedd

Automation of these tasks is achived through the locale

c702b2
functionality of command-line interface (see section trunk/Scripts/Bash/centos-art/Functions/Locale, for more information).
ee1f37

ee1f37
ee1f37
ee1f37
010b2d
[ < ]
010b2d
[ > ]
ee1f37
   
db14a4
[ << ]
010b2d
[ Up ]
193ea4
[ >> ]
ee1f37
ee1f37

ee1f37
 <font size="-1">
010b2d
  This document was generated on February, 28 2011 using texi2html 1.76.
ee1f37
 </font>
ee1f37
 
ee1f37
ee1f37

ee1f37
</body>
ee1f37
</html>