You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2011/12/19 22:10:57 UTC
svn commit: r800537 [8/22] - in
/websites/staging/ooo-site/trunk/content/l10n: ./ L10N_Framework/
L10N_Framework/Examples.inv/ L10N_Framework/ooo20/
L10N_Framework/ooo20/oo_images/ download/ i18n_framework/
i18n_framework/cldr/ localization/ localizati...
Added: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/translate.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/translate.html (added)
+++ websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/translate.html Mon Dec 19 21:10:54 2011
@@ -0,0 +1,2066 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<title>Mozilla PO Tools documentation </title>
+<style>
+<!--
+p.MsoPlainText
+ {margin-bottom:.0001pt;
+ font-size:10.0pt;
+ font-family:"Courier New";
+ margin-left:0in; margin-right:0in; margin-top:0in}
+-->
+</style>
+
+
+</head>
+
+<body>
+ <div id="bannera">
+ <div id="bannerleft">
+ <img id="ooo-logo" alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+ <div id="topbara">
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/l10n/">l10n</a> » <a href="/l10n/L10N_Framework/">L10N_Framework</a> » <a href="/l10n/L10N_Framework/ooo20/">ooo20</a></div>
+ <div id="topnava">
+ <ul>
+<li><a href="/download/index.html" title="Download OpenOffice.org">Download</a></li>
+<li><a href="/support/index.html" title="Find Support for OpenOffice.org">Support</a></li>
+<li><a href="/extensions/index.html" title="Find Extensions and Templates">Extend</a></li>
+<li><a href="http://incubator.apache.org/openofficeorg/get-involved.html" title="Get involved in Apache OpenOffice (incubating)">Develop</a></li>
+<li><a href="/projects/native-lang.html" title="OpenOffice.org in your Native Language">Native Language</a></li>
+</ul>
+ </div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+
+<div align="center">
+ <table border="1" width="90%" id="table18">
+ <tr>
+ <td>
+ <p class="MsoPlainText" align="center"><b>
+ <font face="Arial" style="font-size: 14pt">Traslate Toolkit</font></b></p>
+<p class="MsoPlainText" align="center"> </p>
+<p class="MsoPlainText" align="center"><b>
+<font face="Arial" style="font-size: 14pt">Reference documentation</font></b></p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText" align="center"><b><font face="Arial">For information
+about the tools of the Translate Toolkit, please visit
+<a href="http://translate.sourceforge.net/">http://translate.sourceforge.net/</a>
+</font></b></p>
+ <p class="MsoPlainText" align="center"> </p>
+ <p class="MsoPlainText" align="center"><b>
+ <font face="Arial" size="2">Javier Solá, David Fraser and Dwayne Bailey</font></b></p>
+<p class="MsoPlainText" align="center"> </p>
+ <p class="MsoPlainText" align="center"><b><font face="Arial">Applies to
+Translate Toolkit version 0.8rc2. Last changed on
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->04/23/2005<!--webbot bot="Timestamp" i-checksum="12558" endspan --></font></b></p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText" align="justify"> </p>
+ <p class="MsoPlainText" align="justify">
+ <span style="font-family: Arial">The Translate Toolkit is a set of
+ tools designed to standardise translation of Open Source
+ applications. It permits translating quite a number of Open Source
+ applications using the same translation tools.</span></p>
+ <p class="MsoPlainText" align="justify"> </p>
+ <p class="MsoPlainText" align="justify">
+ <span style="font-family: Arial">It simplifies and facilitate the translation of
+ some of the key end-user OpenSource applications: the OpenOffice application
+suite and applications belonging to the Mozilla family (Mozilla
+suite, Firefox, Thunderbird, etc.).</span></p>
+ <p class="MsoPlainText" align="justify">
+ <span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" align="justify"><span style="font-family: Arial">In all
+these applications, the messages that need to be translated to the target
+language are in specific files (each one with its own format). This Toolkit converts these files into a standard
+format (PO format) that is normally used for translation. The advantage of this
+conversion
+is that there are special editors to translate PO files, making the work of the
+translators very easy, seeing the original and the translation at the same time,
+knowing how much work has been done, saving all messages in a database (translation
+memory) that can be used in other files, etc. Once the files have been
+translated by the translators, tools in the Toolkit are used again to pack the translated files into a format
+that Mozilla or OpenOffice can understand.</span></p>
+ <p class="MsoPlainText" align="justify"> </p>
+ <p class="MsoPlainText" align="justify"><font face="Arial">For
+ localization teams the most important advantage is that anybody
+ doing translation only needs to learn how to use a simple PO file
+ editor (such as poEdit or kBabel), and not a different tool and
+ methodology for each application. PO editors tend to work well with
+ all character sets, including Unicode, and some of them (poEdit, and
+ reportedly now kBabel) work in both the Windows and Linux platforms,
+ not forcing translators to use a specific platform for translation.</font></p>
+<p class="MsoPlainText" align="justify"> </p>
+<p class="MsoPlainText" align="justify"><font face="Arial">The tools are divided
+in three blocks: OpenOffice tools, Mozilla tools and generic support tools.</font></p>
+<p class="MsoPlainText" align="justify"> </p>
+<p class="MsoPlainText" align="justify"><font face="Arial">The Mozilla tools are
+formed by two programs:</font></p>
+<ul>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><b>
+ <font face="Arial" size="2"><a href="#moz2po">moz2po</a> - Converts a Mozilla
+English Language Pack (XPI file) to
+PO format files.</font></b></p></li>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><b>
+ <font face="Arial" size="2"><a href="#Po2moz">po2moz</a> - Converts PO files
+(generated by moz2po and translated) back to Mozilla Language Pack format</font></b></p>
+ </li>
+</ul>
+<p class="MsoPlainText"><font face="Arial">The equivalent programs for
+OpenOffice are:</font></p>
+<ul>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><a href="#moz2po"><b>
+ <font face="Arial">oo</font></b></a><b><font face="Arial" size="2"><a href="#oo2po">2po</a> - Converts
+ OpenOffice GSI (SDF) files to
+PO format files.</font></b></p></li>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><b>
+ <font face="Arial" size="2"><a href="#po2oo">po2oo</a> - Converts PO files
+(generated by oo2po and translated) back to GSI format.</font></b></p></li>
+</ul>
+<p class="MsoPlainText"><font face="Arial">Upgrade tool for both Mozilla and
+openOffice:</font></p>
+ <ul>
+ <li>
+ <p class="MsoPlainText"><font face="Arial"><b><a href="#pot2po">
+ pot2po</a></b> - <b>
+ Upgrade to a new version of PO files for the same product /
+ create PO files from POT files</b></font></p></li>
+ </ul>
+ <p class="MsoPlainText"> </p>
+ <p class="MsoPlainText"><font face="Arial">PO 2 Xliff and viceversa
+ transformation</font></p>
+ <p class="MsoPlainText"> </p>
+ <ul>
+ <li>
+ <p class="MsoPlainText"><font face="Arial">xliff2po</font></p>
+ </li>
+ <li>
+ <p class="MsoPlainText"><font face="Arial">po2xliff</font></p>
+ </li>
+ </ul>
+ <p class="MsoPlainText"> </p>
+ <p class="MsoPlainText"><font face="Arial">Support tools are:</font></p>
+<ul>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><b><font face="Arial">
+ <a href="#pocount">pocount </a>
+ - Count messages in a tree of PO files.</font></b></p></li>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><b>
+ <font face="Arial" size="2"><a href="#PoFilter">pofilter </a> - Finds
+possible errors in PO files</font></b></p></li>
+ <li>
+ <p class="MsoPlainText" style="margin-left: 0"><b>
+ <font face="Arial" size="2"><a href="#PoMerge">PoMerge</a> - Merges translated
+ (corrected) messages
+from a PO file into another PO file.</font></b></p></li>
+</ul>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><font face="Arial"><b><span style="font-size: 14.0pt">
+<a name="moz2po">moz2po</a></span></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This program is part of the Translate Toolkit, a
+package designed to facilitate the translation of Open Source applications to
+new languages. Tools within the package are used to convert the Mozilla type
+files which
+contain translatable messages (.dtd
+and .properties files) to PO format (a standard file format used
+in Open Source). PO files can be easily translated using specialized editors.
+Then these tools are once again used to pack the translated files into a format
+that Mozilla can understand (a XPI Language Pack). They can be used with any of
+the Mozilla family applications (Firefox, Thunderbird, Mozilla, etc.).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">The <b>moz2po</b> program unpacks an original Mozilla
+Language pack (a file with the .xpi extension) into a directory, converting the
+translatable (.dtd and .properties) files into equivalent standard PO files,
+while
+also making available to the translator other files that require changes (in
+order to localize the Language pack). </span>
+</p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">As input it takes a Mozilla American English
+Language Pack. This Language pack is a .XPI file (a zip format compressed file
+that includes all the files that need to be translated or localized).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial" lang="en-au">As output it produces a whole new
+tree (a folder with subfolders inside) that contains all the files from the
+original Language pack (except for .dtd and .properties files, which have been
+translated to PO format). The folder produced contains the following subfolders:</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<ul>
+ <table border="1" width="90%" id="table19">
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <b><font face="Arial">reg</font></b><font face="Arial">
+ </font></p></td>
+ <td><font face="Arial" size="2">contains PO files that need to be
+ translated (which were originally in the US.jar file, inside the .xpi
+ file) and other files to be localised</font></td>
+ </tr>
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>lang-reg</b> </font></p>
+ </td>
+ <td><font face="Arial" size="2">contains PO files that need to
+ be translated (which were originally in the en-US.jar file) and
+ other files to be localised</font></td>
+ </tr>
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>win</b> </font></p></td>
+ <td><font face="Arial" size="2">contains PO files that need to be
+ translated (originally in the en-win.jar file) and other files to be
+ localised.</font></td>
+ </tr>
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>mac</b> </font></p></td>
+ <td><font face="Arial" size="2">contains PO files that need to be
+ translated (originally in the en-mac.jar file) and other files to be
+ localised.</font></td>
+ </tr>
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>unix</b> </font></p></td>
+ <td><font face="Arial" size="2">contains PO files that need to be
+ translated (originally in the en-unix.jar file) and other files to
+ be localised.</font></td>
+ </tr>
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>package</b> </font></p></td>
+ <td><font face="Arial" size="2">contains other files from the .xpi
+ file that need to be localised. It follows the structure of the
+ original XPI file</font></td>
+ </tr>
+ <tr>
+ <td width="90">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>Other folders</b> </font>
+ </p></td>
+ <td><font face="Arial" size="2">may contains PO files that need to
+ be translated and other files to
+ be localised.</font></td>
+ </tr>
+ <tr>
+ <td width="90" height="22">
+ <p class="MsoPlainText" style="text-align: justify">
+ <font face="Arial"><b>Template</b> </font></p>
+ </td>
+ <td height="22"><font face="Arial" size="2">contains a copy of the original
+ English .xpi file, used later by po2moz to build the .xpi file for
+ the target language. Do not touch it.</font></td>
+ </tr>
+ </table>
+</ul>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> <b>moz2po</b> can also be used to convert to PO
+format a <b>language pack</b> that is already translated. As the language pack for your
+language does not have the English original messages (needed for the PO file),
+it also needs to use an original English language pack (en-US.xpi) as a
+template, so that it will have all the information needed for the PO files. This
+conversion (to PO format) permits the use of the information contained in the Mozilla files
+with a Translation Memory tool that uses PO files as input.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial"><b>moz2po</b> other use is to convert any tree of files that
+includes .dtd files and .properties files into another tree with identical
+structure that includes all the same files of the original tree, except that all
+these .dtd and .properties files are converted to PO files with the same name
+and with the to .dtd.po and .properties.po extensions. </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial">This last application is useful for the new localization packs
+used in Mozilla products for CVS based localization. The Mozilla Foundation
+produces ZIP files that include a tree of files identical to the tree used for
+localization of a given language in the Mozilla-product CVS. Once localized,
+this packaged can be directly uploaded to CVS, and the Mozilla Foundation will
+produce the local language executable packages, as well as the installers.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This function <b>must be used only once</b>,
+before starting the translations. If it is used again once some of the PO files
+have been translated, it will overwrite the translated files with empty PO
+files, having to start the translation again.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial"><b>Note:</b> the format of the generated PO files is UTF-8,
+which allows this files to be translated to any language that uses Unicode. When
+translated back to ,dtd and .properties formats, .dtd files are generated in
+UTF-8 format, and .properties files in Escaped Unicode format, as required by
+Mozilla applications.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">Different syntax is given for the different
+uses of the program:</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Conversion of an original English XPI file into a tree of .po files
+and other localizable files</span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: moz2po [options] INPUT OUTPUT</i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="center">
+ <table border="0" id="table20">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font size="2"><font face="Arial">
+</font><span style="font-family: Arial">is the filename (xpi extension included)</span><font face="Arial">
+</font></font><span style="font-family: Arial"><font size="2">of an original English language pack (an XPI file) belonging to an application of the Mozilla family (Mozilla, Firefox,
+Thunderbird, Camino). </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the directory inside which all the subfolders with the equivalent PO files,
+and all other information will be placed.
+If the folder itself does not exist, it will be created by moz2po. If the folder
+exists already, files inside might be overwritten. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -P</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Produce PO template (.pot) files instead of Po files (.po), but the contents of
+the file is exactly the same. (note: .pot files are sometimes interpreted by MS
+Windows as PowerPoint template files, pay no attention to this).</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Examples:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 251.0pt">
+<span lang="ES" style="font-family: Arial">moz2po i en-US.xpi o locale</span></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">This command creates - based on the en-US.xpi
+original English pack - the tree described above under the <b>locale</b> name,
+containing the structure of the package (in the locale\package subfolder), a
+copy of the en-US.xpi file in the locale\template sub-folder (to be used for
+repackaging), and other subfolders that contain PO files that need to be
+translated and other files which might need to be localised (locale\reg, locale\lang-reg,
+locale\win, etc.).</span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Conversion (migration) of an already translated
+language pack into a PO files and other localized files </span></b></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: moz2po [options] -i INPUT -o OUTPUT t TEMPLATE</i></b></font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"> </font></p>
+<div align="center">
+ <table border="0" id="table21">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<font face="Arial" size="2">INPUT is the filename (xpi extension included) of a
+ language pack of a given Mozilla family application that has already
+ been translated into your language. It must have exactly the same
+ structure as the original English pack used as TEMPLATE.</font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the directory inside which all the subfolders with the equivalent PO files,
+and all other information will be placed.
+If the folder itself does not exist, it will be created by moz2po. If the folder
+exists already files inside might be overwritten. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font size="2"> </font>
+ <font size="2" face="Arial"> TEMPLATE</font></td>
+ <td>
+<font face="Arial" size="2">TEMPLATE is an original English language pack (an XPI
+ file) for the same Mozilla family application (and same program
+ version) than the package that is used as INPUT.</font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-align: justify"> </p>
+<p class="MsoPlainText"><font face="Arial">Example:</font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<pre style="font-size: 10.0pt; font-family: Arial; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt">moz2po -i km-KH.xpi -o locale -t en-US.xpi</pre>
+<pre style="font-size: 10.0pt; font-family: Arial; margin-left: 0in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"> </pre>
+<p style="font-size: 10.0pt; font-family: Arial; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt" class="MsoPlainText">
+This program takes the Khmer language pack for a Mozilla application (km-KH.xpi)
+and the original US English language pack for the same application (and version,
+en-US.xpi) and creates a directory of PO files that have in the original string
+(msgid) the English original and in the translation string (msgstr) the Khmer
+translation. </p>
+<pre style="font-size: 10.0pt; font-family: Arial; margin-left: 0in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"> </pre>
+<p class="MsoPlainText" style="font-size: 10.0pt; font-family: Arial; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"> This
+command creates - based on the km-KH.xpi file (an XPI language pack for Khmer
+language) and the en-US.xpi original English pack - the tree described above
+under the <b>locale</b> name, containing the structure of the km-KH.xpi package
+(in the locale\package subfolder), a copy of the en-US.xpi file in the
+locale\template sub-folder (to be used for repackaging), and other subfolders
+that contain PO files that already contain the translated strings from km-KH.xpi
+and other files which have already been localised in km-KH.xpi (such as
+contents.rdf files) These directories are named locale\reg, locale\lang-reg,
+locale\win, etc.</p>
+ <p><b>Conversion a tree that contains .dtd. and .properties files into a
+similar tree in which these files are turned into PO files.</b></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: moz2po [options] INPUT OUTPUT</i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="center">
+ <table border="0" id="table22">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font size="2"><font face="Arial">
+</font><span style="font-family: Arial">is the name of the folder that contains
+ the tree of files that need to be converted to PO</span></font><span style="font-family: Arial"><font size="2">. </font> </span>
+ </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the folder
+ in which the output tree with all the PO files will be created. If the folder
+exists already files inside might be overwritten. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -P</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Produce PO template (.pot) files instead of Po files (.po), but the contents of
+the file is exactly the same. (note: .pot files are sometimes interpreted by MS
+Windows as PowerPoint template files, pay no attention to this).</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Example:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 251.0pt">
+<span lang="ES" style="font-family: Arial">moz2po i EnglishTree o localeTree</span></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">This instruction copies all the EnglishTree
+folder and its contents into localeTree, maintaining the subfolder structure.
+All files are copied to the second tree, except for .dtd and .properties files,
+which are replaced in the localeTree folder by their equivalent PO files with
+extensions .dtd.po and .properties.po</span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p><p class="MsoPlainText"> </p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><font face="Arial"><b>
+<span style="font-size: 14.0pt"><a name="Po2moz">Po2moz</a></span></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This program is part of the Translate Toolkit, a
+package designed to facilitate the translation of Open Source applications to
+new languages. Tools within the package are used to convert the Mozilla type
+files which
+contain translatable messages (.dtd
+and .properties) to PO format (a standard file format used
+in Open Source). PO files can be easily translated using specialized editors.
+Then these tools are once again used to pack the translated files into a format
+that Mozilla can understand (a XPI Language Pack). IT can be used with any of
+the Mozilla family applications (Firefox, Thunderbird, Mozilla, etc.).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">Once the user has created a tree of localizable
+files using <b>moz2po</b>, and translated and localized everything that was
+required, <b>po2moz</b> takes all this tree again and converts it to a Language
+pack for your language. </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial">The name of the locale of a language pack is used often
+inside the language pack. This name (<LanguageCode-RegionCode>, as en-US, km-KH,
+af-ZA, etc.) is passed to <b>po2moz</b> as an argument, and <b>po2moz</b> takes
+care of inserting it in file names or folder names in the destination pack when
+this is necessary.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial"><b>po2moz</b> can also be used to convert any tree of files
+that includes .dtd.po files and .properties.po files to another identical tree
+that includes the all the same files of the original tree, except that all these
+PO files are converted to .dtd and .properties files. This is useful for the new
+localization packs used in Mozilla products for CVS based localization. The
+Mozilla Foundation produces ZIP files that include o tree of files identical to
+the tree used for localization of a given language in the Mozilla-product CVS.
+The tree in these packs is converted to a tree that contains PO files using the
+moz2po tool, and after translation and localization, the tree is converted again
+with po2moz into a tree that contains translated .dtd and .properties files...
+and which can be uploaded directly into CVS.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">In order to assure that all the original
+information from the original .dtd or .properties files is put into the newly
+generated file, it uses as templates the original .dtd and .properties files
+that are in the original folder from which the .po files where generated. Files
+in the target directory are re-written if the program is run more than once, but
+this does not have any side-effects, as the files are generated always from the
+PO files.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align:justify"><b>
+<span style="font-family:"Arial"">Note:</span></b><span style="font-family:"Arial"">
+PO files include the & character to specify that a given shortcut can be used
+(it does not always indicate this, when it followed by a word and a semicolon it
+indicates a variable name). The & indicates that the next character can be
+used as a shortcut. This shortcut character can be changed when editing to PO
+file, and a different character can be used for the short. If the & character
+is not present in the translation, <b>po2moz</b> will automatically include the old
+shortcut in the final .dtd file.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">Different syntax is given for the different
+uses of the program:</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText"><b><font face="Arial">Creation of an XPI file from
+localized PO files: </font></b></p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><font face="Arial"><b><i>usage: po2moz
+[options]-i INPUT -o OUTPUT -l LOCALE</i></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<div align="center">
+ <table border="0" id="table23">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<font face="Arial" size="2">INPUT is the folder that contains all the
+ information that will go into the XPI file. This folder was created
+ by moz2po, and, as reference, is the folder that contains the
+ subfolders reg, reg-lang, package, template, etc.</font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the XPI file (including the .xpi extension) to be generated with all the
+translated and localised files.</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font size="2"> </font>
+ <font size="2" face="Arial"> LOCALE</font></td>
+ <td><font face="Arial" size="2">LOCALE is the locale used in the new
+ XPI file. It has the format xx-RR, where xx is the two character
+ ISO-639 code for the target language (if there is a two character
+ code, otherwise it would be xxx-RR, where xxx is three letter
+ character code for the language), and RR is the two letter ISO-3166
+ code for the country or region. See
+ <a href="http://www.loc.gov/standards/iso639-2/">
+ http://www.loc.gov/standards/iso639-2/</a> and </font>
+ <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html">
+ http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</a>
+ if you need more information.</td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> <font face="Arial" size="2">
+ - x EXCLUDED</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">EXCLUDED can be a file or a
+ folder name. If it is a file, it is not included in the XPI file, if
+ it is a folder, any files or subfolder that are contained in the
+EXCLUDED folder are not included in the XPI file. This can be used when there is additional information in the
+original XPI that is not desired in the final XPI, such as CVS information. You
+can use wildcards, if you enclose the filename in with quotes. </font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-align: justify; text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: 0in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial">Example:</span></pre>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: 0in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial"> </span></pre>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial">po2moz -x CVS -x '*.diff" -i locale -o firefox1.0RC.km-KH.xpi -l km-KH</span></pre>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial"> </span></pre>
+<p style="font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: 0pt" class="MsoPlainText">
+<span style="font-family: Arial"><font size="2">It takes the (already created
+with <b>moz2po</b> and translated) PO files contained in the <b>locale</b>
+directory, converts them to the original .dtd and .properties formats and with
+them it creates a language pack called firefox1.0RC.km-KH.xpi for the target
+language. In this package, locale sensible file names and directory names use KH
+as the region name and km-KH as the full locale name when needed. Do not include
+in the XPI files and directories called CVS, nor files with the "diff"
+extension.</font></span></p>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"> </pre>
+<p class="MsoPlainText"><b><font face="Arial">Creation of a tree that contains
+translated .dtd. and .property files from localized PO files: </font></b></p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><font face="Arial"> <b><i>usage: po2moz
+[options] -i INPUT -o OUTPUT -t TEMPLATE</i></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<div align="center">
+ <table border="0" id="table24">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<font face="Arial" size="2">INPUT is the folder that contains, directly or in
+ subfolders, translated .dtd.po and .properties.po files, as well as
+ other files needed for localization. </font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of folder in
+ which the program will create a folder identical to the INPUT
+ folder, except that .dtd.po files will be converted to .dtd files
+ and .properties.po files will be converted to .properties files.</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font size="2"> </font>
+ <font size="2" face="Arial"> TEMPLATE</font></td>
+ <td>TEMPLATE is the original directory from which the INPUT
+ directory was created (by using the moz2po program). It includes the
+ original .dtd and .properties files in English. It is used to assure
+ that the generated .dtd and .properties files are identical in
+ structure to the original ones (to include information that could
+ not be stored in the PO files).</td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> <font face="Arial" size="2">
+ - x EXCLUDED</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">EXCLUDED can be a file or a
+ folder name. If it is a file, it is not included in the XPI file, if
+ it is a folder, any files or subfolder that are contained in the
+EXCLUDED folder are not copied to the OUTPUT folder. This can be used when there is additional information in the
+original folder that is not desired in the finalone, such as CVS information.
+You can use wildcards, if you enclose the filename in with quotes. </font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-align: justify; text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: 0in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial">Example:</span></pre>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: 0in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial"> </span></pre>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial">po2moz -i locale -o firefox1.0RC-kmKH -t firefox1.0RC-enUS</span></pre>
+<pre style="font-size: 10.0pt; font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt"><span style="font-family: Arial"> </span></pre>
+<p style="font-size: 10.0pt; font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: .0001pt" class="MsoPlainText">
+<span style="font-family: Arial">It takes the (already translated) PO files
+contained in the <b>locale</b> directory, converts them to the original .dtd and
+.properties formats (with the help of the files contained in the original <b>
+firefox1.0RC-enUS</b> folder) and creates a new folder called <b>firefox1.0RC-kmKH</b>,
+identical in structure to <b>locale</b> and to <b>firefox1.0RC-enUS</b> folders,
+in which instead of PO files there are translated .dtd and .properties files.</span></p>
+<p style="font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: 0pt" class="MsoPlainText">
+ </p>
+<p style="font-family: Courier New; margin-left: .5in; margin-right: 0in; margin-top: 0in; margin-bottom: 0pt" class="MsoPlainText">
+ </p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><font face="Arial"><b><span style="font-size: 14.0pt">
+<a name="oo2po">oo2po</a></span></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This program is part of the Translate Toolkit, a
+package designed to facilitate the translation of Open Source applications to
+new languages. Tools within the package are used to convert the Mozilla and
+OpenOffice type
+files which
+contain translatable messages (.dtd, .properties or GSI files) to PO format (a standard file format used
+in Open Source). PO files can be easily translated using specialized editors.
+Then these tools are once again used to pack the translated files into a format
+that Mozilla or OpenOffice can understand (a XPI Language Pack or a GSI file). The
+Toolkit can be used for OpenOffice or for any of
+the Mozilla family applications (Firefox, Thunderbird, Mozilla, etc.).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">The <b>oo2po</b> program converts an OpenOffice
+GSI file (a file that contains all the messages used by OpenOffice) into a set of
+manageable POT files (PO templates, empty PO files) that can be easily used by
+translators, even distributed among several traslators (which would not be the
+case if only one large PO file had been created). These files are stored in a tree of folders. Once they have
+been translated, the <b>po2oo</b> tool can be used to convert the files back to GSI
+format, the format accepted by the OpenOffice project. It is nevertheless
+advisable to run <b>pofilter</b> before you convert back, to make sure that your
+files do not have any outstanding problems.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial">The <b>oo2po</b> utility has now been integrated in the OpenOffice
+build process. PO files for each version of OOo are produced directly by
+OpenOffice.org. This means that you (as a localizer) will normally not need to
+run this program.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">As input, <b>oo2po</b> takes the GSi file
+corresponding to the version of OpenOffice that you wish to translate. If you
+are creating POT files, the GSI files only need to contain the English language.
+Nevertheless, it is also possible to have POT files in which the reference
+language used in the msgid fields of the PO files is other than English. In
+order to do this, it is necessary to have a GSI file that includes the language
+that you want to use as reference. This is very useful for countries in which
+the second language is French, Russian or some language other than English.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial" lang="en-au">As output it produces a whole new
+tree (a folder with subfolders inside) that contains one POT file for each part
+of OpenOffice.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<b><span style="font-family: Arial">oo</span></b><span style="font-family: Arial"><b>2po can also be used to convert to PO
+format GSI files that are already totally or partially translated to your
+language</b>. In order to do this, you need to have a GSI file that has -at
+least- English and your language. oo2po will create files that have the original
+language as msgid and your languages in the msgstr.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">In this second case, this function <b>must be used only once</b>,
+before starting the translations. If it is used again once some of the PO files
+have been translated, it will overwrite the PO files that you have worked on
+with PO
+files created again fom the GSI, having to start the translation again.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial"><b>Note:</b> the format of the generated PO files is UTF-8,
+which allows this files to be translated to any language that uses Unicode.</font><span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial">As in the case of generating POT files, oo2po also permits using
+here as reference a language (in the msgid) different from English. For this it
+is necessary to have a GSI file that includes both the language that will be
+used as reference in the msgid and the target language that will be placed in
+the msgstr fields.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Conversion of an original English GSI file into a tree of .po files
+</span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: oo2po [options] -P INPUT OUTPUT</i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="center">
+ <table border="0" id="table25">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font size="2"><font face="Arial">
+</font><span style="font-family: Arial">is the filename </span></font><span style="font-family: Arial"><font size="2">of the original
+English GSI file for the version that you with to translate. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the directory inside which all the subfolders with the equivalent PO files will be placed.
+If the folder itself does not exist, it will be created by oo2po. If the folder
+exists already, files inside will be overwritten. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -P</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2"> Produce PO template (.pot) files instead of Po files (.po), but the contents of
+the file is exactly the same. (note: .pot files are sometimes interpreted by MS
+Windows as PowerPoint template files, pay no attention to this). This argument
+is mandatory when producing only English files (with empty translations).</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --source-language=ISO</font></td>
+ <td>
+<font size="2"><span style="font-family: Arial">This option permits using a
+language different than US English as reference for the POT files (the language
+in which the messages are placed in the msgid field of the POT files). ISO is
+the OpenOffice ISO code of the language that will be used as reference in the
+msgid fields of the POT file. In order to use this option it is necessary to
+have an SDF file that contains that language specified in this option. If this
+option is not used, the default reference language is en_US (US English).</span></font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Examples:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">moz2po -P en_US.sdf locale </font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">This command creates - based on the en_US.sdf
+original English GSI file - a folder called <b>locale</b> with subfolders that
+contain all the POT (PO template) files needed by that version of OpenOffice,
+including helpfiles. These POT files are empty PO files that need to have their
+extension changed to .po when their transaltion start.</span></p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">oz2po -P en_US_and_French.sdf locale
+--source-language=fr_FR</font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">This command creates - based on the en_US_and_french.sdf
+GSI file (which contains at least the English and French messages) - a folder called <b>locale</b> with subfolders that
+contain all the POT (PO template) files needed by that version of OpenOffice,
+including helpfiles. These POT files are empty PO files that need to have their
+extension changed to .po when their transaltion start. As reference language in
+the msgid fields it has French French (fr_FR), as spoken in France itself!!</span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Conversion of an GSI file that has English (or
+other reference language) and
+-at least- another language into a tree of .po files that have all the available
+translations to that second language.</span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: oo2po [options] -i INPUT -o OUTPUT -l LOCALE_CODE
+[--source-language=ISO]</i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="center">
+ <table border="0" id="table26">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font size="2"><font face="Arial">
+</font><span style="font-family: Arial">is the filename </span></font><span style="font-family: Arial"><font size="2">of the original
+English GSI file for the version that you with to translate. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the directory inside which all the subfolders with the equivalent PO files will be placed.
+If the folder itself does not exist, it will be created by oo2po. If the folder
+exists already, files inside will be overwritten. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -l LOCALE_CODE</font></td>
+ <td>
+<font size="2"><span style="font-family: Arial">OpenOffice locale code for the
+translation that you want to place into the pre-translated PO files</span></font><span style="font-family: Arial"><font size="2">.</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --source-language=ISO</font></td>
+ <td>
+<font size="2"><span style="font-family: Arial">This option permits using a
+language different than US English as reference for the PO files (the language
+in which the messages are placed in the msgid field of the PO files). ISO is the
+OpenOffice ISO locale code of the language that will be used as reference in the
+msgid fields of the PO file. In order to use this option it is necessary to have
+an SDF file that contains that language specified in this option. If this option
+is not used, the default reference language is en_US (US English).</span></font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Example:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">oo2po -i en_US_and_km.sdf -o locale -l km</font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">This command creates - based on a GSi file that
+contains the original English and Khmer (partial or complete) translation
+(en_US_and_km.sdf) - a folder called <b>locale</b> with subfolders that contain
+all the PO files needed by that version of OpenOffice, including helpfiles.
+These PO files contain the original English in the msgid string and translations
+to Khmer (km) in the msgstr for the strings that it is available. Other strings
+are empty.</span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">oo2po -i en_US_and_pt_PT_some_pt_BR.sdf -o locale -l
+pt_BR --source-language=pt_PT</font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">This command creates - based on a GSi file that
+contains the original English and Portuguese Portuguese (complete) translations,
+as well as some Brazilian Portuguese
+(</span><i><font face="Arial">en_US_and_pt_PT_some_pt_BR.sdf</font></i><span style="font-family: Arial">) - a folder called <b>locale</b> with subfolders that contain
+all the PO files needed by that version of OpenOffice, including helpfiles.
+These PO files contain the original Portuguese Portuguese (pt_PT) in the msgid string and translations
+to Bazilian Portuguese (pt_BR) in the msgstr for the strings that it is available. Other strings
+are empty.</span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText"><a name="oo2po0"><b>
+<font face="Arial" style="font-size: 14pt">p</font></b></a><font face="Arial"><b><span style="font-size: 14.0pt"><a name="po2oo">o2oo</a></span></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This program is part of the Translate Toolkit, a
+package designed to facilitate the translation of Open Source applications to
+new languages. Tools within the package are used to convert the Mozilla and
+OpenOffice type
+files which
+contain translatable messages (.dtd, .properties or GSI files) to PO format (a standard file format used
+in Open Source). PO files can be easily translated using specialized editors.
+Then these tools are once again used to pack the translated files into a format
+that Mozilla or OpenOffice can understand (a XPI Language Pack or a GSI file). The
+Toolkit can be used for OpenOffice or for any of
+the Mozilla family applications (Firefox, Thunderbird, Mozilla, etc.).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">The <b>po2oo</b> program converts a tree of PO
+files (that was either generated by <b>oo2po</b> or taken from the OpenOffice website,
+and then translated and filtered) into a GSI file that can be integrated into
+OpenOffice (a file that contains all the messages used by OpenOffice in a format
+that makes their integration easy).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">As input, <b>po2oo</b> takes the folder (the tree)
+that contains all your PO files.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<font face="Arial">In order to make sure that the file generated is equivalent
+to the original one, the exact original (same version) English GSI file that was
+used to generate the POs by <b>oo2po</b> is used here as a template.</font></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial" lang="en-au">As output it produces a GSI file
+that can be automatically integrated in OpenOffice.</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span lang="en-au"><font face="Arial">Inside the file, it is necessary to
+include the locale definition for which the messages are, this is done using the
+-l option.</font></span></p>
+<p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify">
+<span lang="en-au"><font face="Arial">By default, po2oo does not include in the
+final GSI file translations that are marked as fuzzy in the PO file, it includes
+the English original message instead. If it is considered better to include
+these translations, the --fuzzy option needs to be used.</font></span></p>
+ <p class="MsoPlainText" style="text-align: justify">
+ </p>
+ <p class="MsoPlainText" style="text-align: justify">
+<span lang="en-au"><font face="Arial">If a reference language different than
+English was used for generating the PO files that we are working with (the
+--source-language option was used in oo2po), then it is necessary to again
+specify this language in po2oo, using the same --source-language option, with
+exactly the same locale code that was used in oo2po.</font></span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Conversion of translated PO files into an
+OpenOffice native GSI file </span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: po2oo [options] -i INPUT -o OUTPUT -t TEMPLATE -l LOCALE
+[--source-language==ISO]</i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="center">
+ <table border="0" id="table27">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font face="Arial" size="2">
+</font>
+<span style="font-family: Arial"><font size="2">is the name (path) of the
+directory inside which all the subfolders with the PO files are located. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top">
+ <font face="Arial" size="2">TEMPLATE</font></td>
+ <td>
+TEMPLATE is the name (path) of the original GSI file that was used to generate
+the PO files that you are not converting back.</td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the GSI
+file that will be created. It is a good idea to use the .sdf extension, as it
+defines the format. If the file
+exists already, it will be overwritten. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ LOCALE</font></td>
+ <td>
+<font size="2"><span style="font-family: Arial">Locale is the name of the locale
+that you are transalting for. It is either the two-letter (or three-letter if
+there is no two-letter) language code, or the mentioned language code, a hyphen,
+and the country code. Examples are km, es-CL, ta-IN... The languages page of
+OpenOffice defines the locale for each project. For versions of OpenOffice prior
+to 2.0 (1.1.x), this is actually a number assigned by OpenOffice to the project,
+and which can also be found in the languages page of OpenOffice.</span></font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --source-language=ISO</font></td>
+ <td>
+<font size="2"><span style="font-family: Arial">This option must be used if a
+language different than US English is used as a reference in the msgid of the PO
+files that are being used as input (this only happens if the --source-language
+option was used in oo2po when the PO or POT files were enerated). ISO is
+the OpenOffice ISO locale code of the language that is used as reference in the
+msgid fields of the PO file, it has to exactly the same that was used in oo2po
+when these PO or POT files we generated. If the option is not used, the default
+reference language is assumed to be en_US (US English).</span></font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font size="2">
+ <span style="font-family: Arial"> --fuzzy</span></font></td>
+ <td>
+<font size="2"><span style="font-family: Arial">When this option is included,
+translations that in the PO files are considered as "fuzzy", will be included in
+the GSI file generated by po2oo. If it is not used, fuzzy translation will not
+be included (the original English message is included instead). A message is
+considered as fuzzy when, in the PO file, the message is preceeded by the line
+"#, fuzzy".</span></font></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> -x EXCLUDED</td>
+ <td>
+<span style="font-family: Arial"><font size="2">EXCLUDED can be a file or a
+ folder name. If it is a file, it is not taken into account for the
+ GSI file, if it is a folder, any files or subfolder that are
+ contained in the EXCLUDED folder are not used to build the OUTPUT
+ file. This can be used when there is additional information in the
+ original folder that is not desired in the OUTPUT file, such as CVS
+ information. You can use wildcards, if you enclose the filename in
+ with quotes. </font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Example:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">oo2po -x CVS -x '*.diff' i locale t en_US.sdf -o
+en_CL.sdf -l en-CL</font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">Given a directory called locale that contains
+all the OOo PO files that have been translated to your language, and given
+en_US.sdf, the original GSI file from which those PO files were
+originated,create a new GSI file with the translations called es_CL.sdf, using
+the locale code es-CL inside that file. Ignore files and directores called CVS or
+files that have the .diff extension.</span></p>
+<p class="MsoPlainText"> </p>
+ <p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><font face="Arial"><b><span style="font-size: 14.0pt">
+<a name="pot2po">pot2po</a></span></b></font></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This program is part of the Translate Toolkit, a
+package designed to facilitate the translation of Open Source applications to
+new languages. Tools within the package are used to convert the Mozilla and
+OpenOffice type
+files which
+contain translatable messages (.dtd, .properties or GSI files) to PO format (a standard file format used
+in Open Source). PO files can be easily translated using specialized editors.
+Then these tools are once again used to pack the translated files into a format
+that Mozilla or OpenOffice can understand (a XPI Language Pack or a GSI file). The
+Toolkit can be used for OpenOffice or for any of
+the Mozilla family applications (Firefox, Thunderbird, Mozilla, etc.).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">The <b>pot2po</b> program has two possible
+funtions: </span></p>
+ <ol>
+ <li>
+ <p class="MsoPlainText" style="text-align: justify">
+ <span style="font-family: Arial">Given the PO files for an
+ application that have already been translated, and POT files for
+ a newer version of the same application, create a set of PO
+ files for the new version that include all the translations that
+ were already in the PO files for the old version.</span></p>
+ </li>
+ <li>
+ <p class="MsoPlainText" style="text-align: justify">
+ <span style="font-family: Arial">Given a tree that contains POT
+ files, it creates an identical tree, with the same files, but
+ the extension on the files of the new tree will be ".po",
+ instead of ".pot". </span></p></li>
+ </ol>
+ <p class="MsoPlainText" style="text-align: justify">
+<font face="Arial">It takes as INPUT the name of the folder that contains the
+POT files, as OUTPUT the name of the folder to which the PO files will be
+created, and as a TEMPLATE the directory that contains the PO files for the old
+version of the same product.</font></p>
+ <p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Upgrade an applications PO files to the new
+version, maintaining the translations </span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: pot2po [options] -i INPUT -o OUTPUT -t TEMPLATE </i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="center">
+ <table border="0" id="table30">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font face="Arial" size="2">
+</font>
+<span style="font-family: Arial"><font size="2">is the name (path) of the
+folder that contains the POT files for the new version of the application. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the folder
+to which the PO files for the new version will be written, containing also all
+translated messages that were already translated in the PO files of the old
+version (PO files that are in the TEMPLATE directory). The program will create
+in OUTPUT a tree identical to the tree in INPUT. If a file is present in INPUT,
+but not present in TEMPLATE, an empty copy of the POT file will be generated as
+PO file in the OUTPUT folder. If the TEMPLATE and OUTPUT folders are the same,
+the old PO files will be replaced by the upgraded ones.</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top">
+ <font face="Arial" size="2">TEMPLATE</font></td>
+ <td>
+TEMPLATE is the name (path) of the folder that contains the PO files for the old
+version of th eprogram, from which we desire to recover the already translated
+messages.</td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Example:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">pot2po i new_version_pots t old_version_pos -o
+new_version_pos</font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">Given a set of already translated PO files for
+a product A, localed in the folder <i>old_version_pos</i>, and a set of POT
+files for a newer version of the same product A, in folder <i>new_version_pots</i>
+(both trees being identical), a new tree is created in <i>new_version_pos</i>
+that has copies of all the files in <i>new_version_pots</i>, but the new files
+have ".po" extensions. All translated messages that have been found in the same
+files in <i>old_version_pos</i> have been copied into these new files. As a
+result, <i>new_version_pos</i> contains the PO files for the new version,
+and only new messages that were not present in the old version need to be
+translated now.</span></p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+<p class="MsoPlainText"> </p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Create PO files from a set of POT files</span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: pot2po [options] -i INPUT -o OUTPUT </i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="left">
+ <table border="0" id="table31">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ INPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font face="Arial" size="2">
+</font>
+<span style="font-family: Arial"><font size="2">is the name (path) of the
+folder that contains the POT files</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ OUTPUT</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">OUTPUT is the name of the folder
+to which the PO files will be written</font></span>.</td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> --csv</td>
+ <td>
+Produce output in CSV format (comma separated), one line per file, so that it
+can be inported into a spreadsheet.</td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Example:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">pot2po i pot_files -o
+po_files</font></i></p>
+<p class="MsoPlainText"><span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">Given set of POT files in folder <i>po_files</i>,
+create an equivalent set of PO files in folder <i>po_files</i>.</span></p>
+ <p class="MsoPlainText"> </p>
+ <p class="MsoPlainText"> </p>
+<p class="MsoPlainText"><b><font face="Arial" style="font-size: 14pt">
+<a name="pocount">PoCount</a></font></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">This program is part of the Translate Toolkit, a
+package designed to facilitate the translation of Open Source applications to
+new languages. Tools within the package are used to convert the Mozilla and
+OpenOffice type
+files which
+contain translatable messages (.dtd, .properties or GSI files) to PO format (a standard file format used
+in Open Source). PO files can be easily translated using specialized editors.
+Then these tools are once again used to pack the translated files into a format
+that Mozilla or OpenOffice can understand (a XPI Language Pack or a GSI file). The
+Toolkit can be used for OpenOffice or for any of
+the Mozilla family applications (Firefox, Thunderbird, Mozilla, etc.).</span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-align: justify">
+<span style="font-family: Arial">The <b>pocount</b> program counts the number of
+messages and words (translatable words words included in the messages) in a PO
+(or POT) file or in a folder or tree containing PO (or POT) files. </span></p>
+ <p class="MsoPlainText" style="text-align: justify">
+ </p>
+<p class="MsoPlainText" style="text-align: justify"><b>
+<span style="font-family: Arial">Count the number of messages and words.</span></b></p>
+<p class="MsoPlainText"><font face="Arial"> </font></p>
+<p class="MsoPlainText" style="text-align: justify"><font face="Arial"><b><i>
+usage: pocount [options] PATH</i></b></font></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<div align="left">
+ <table border="0" id="table32">
+ <tr>
+ <td width="153"><font face="Arial" size="2">Arguments (mandatory):</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ PATH</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">INPUT</font></span><font face="Arial" size="2">
+</font>
+<span style="font-family: Arial"><font size="2">is the name of the file or
+folder in which we desire to count messages. </font> </span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"> </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">Options:</font></td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ --version</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show program's version
+number and exit</font></span></td>
+ </tr>
+ <tr>
+ <td width="153" valign="top"><font face="Arial" size="2">
+ -h</font></td>
+ <td>
+<span style="font-family: Arial"><font size="2">Show a help with the programs
+ usage syntax and exit</font></span></td>
+ </tr>
+ </table>
+</div>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+ </p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial">Example:</span></p>
+<p class="MsoPlainText" style="text-indent: -215.0pt; margin-left: 215.0pt">
+<span style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<i><font face="Arial">pocount afile.po</font></i></p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span lang="ES" style="font-family: Arial"> </span></p>
+<p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial">Returns the number of messages and translatable
+words in the afile.po file.</span></p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+<span style="font-family: Arial; font-style: italic">pocount po_folder</span></p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
+ </p>
+ <p class="MsoPlainText" style="text-indent: 1.0pt; margin-left: 35.0pt">
[... 415 lines stripped ...]