Blame Manual/repository-html/repository_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
-->
406f69
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>
861ed3
<title>CentOS Artwork Repository: 1.36 The trunk/Locales Directory</title>
ee1f37
861ed3
<meta name="description" content="CentOS Artwork Repository: 1.36 The trunk/Locales Directory">
861ed3
<meta name="keywords" content="CentOS Artwork Repository: 1.36 The trunk/Locales Directory">
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
aaf678
[ < ]
aaf678
[ > ]
ee1f37
   
aaf678
[ << ]
aaf678
[ Up ]
aaf678
[ >> ]
ee1f37
   
ee1f37
   
ee1f37
   
ee1f37
   
56a476
[Top]
56a476
[Contents]
5cb5a7
[Index]
56a476
[ ? ]
ee1f37
aaf678
982d5c
861ed3

1.36 The <tt>`trunk/Locales'</tt> Directory

aaf678
aaf678

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

aaf678
messages used to produce content in different languages.
aaf678

aaf678

Translation messages are organized using the directory structure of

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

aaf678

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

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

aaf678

The basic translation process is as follow: first, translatable

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

aaf678

Inside the repository there are two ways to retrive translatable

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

aaf678

When translatable strings are retrived from XML files, using the

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

aaf678

Another difference between xml2po and xgettext we

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

aaf678

Automation of localization tasks is achived through the locale

aaf678
functionality of command-line interface.
aaf678

aaf678
861ed3
1.54 The <tt>`trunk/Scripts/Bash/Cli/Functions/Locale'</tt> Directory  
aaf678
aaf678
fd83ec
ee1f37
ee1f37
ee1f37
aaf678
[ < ]
982d5c
[ > ]
ee1f37
   
aaf678
[ << ]
aaf678
[ Up ]
aaf678
[ >> ]
ee1f37
ee1f37

ee1f37
 <font size="-1">
406f69
  This document was generated on March, 1 2011 using texi2html 1.76.
ee1f37
 </font>
ee1f37
 
ee1f37
ee1f37

ee1f37
</body>
ee1f37
</html>