incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r800537 [5/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...
Date Mon, 19 Dec 2011 21:10:57 GMT
Added: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/localization_tips.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/localization_tips.html (added)
+++ websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/localization_tips.html Mon Dec 19 21:10:54 2011
@@ -0,0 +1,417 @@
+<!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-Language" content="en-us">
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<title>Localization tips for OpenOffice.org 2.0</title>
+<style>
+<!--
+p
+  {margin-right:0in;
+  margin-left:0in;
+  font-size:12.0pt;
+  font-family:"Times New Roman";
+  }
+div.Section1
+  {page:Section1;}
+ p.MsoNormal
+  {mso-style-parent:"";
+  margin-bottom:.0001pt;
+  font-size:10.0pt;
+  font-family:"Times New Roman";
+  margin-left:0in; margin-right:0in; margin-top:0in}
+h3
+  {margin-top:12.0pt;
+  margin-right:0in;
+  margin-bottom:3.0pt;
+  margin-left:0in;
+  page-break-after:avoid;
+  font-size:13.0pt;
+  font-family:Arial;
+  font-weight:bold}
+ li.MsoNormal
+  {mso-style-parent:"";
+  margin-bottom:.0001pt;
+  font-size:10.0pt;
+  font-family:"Times New Roman";
+  margin-left:0in; margin-right:0in; margin-top:0in}
+p.tablehead-western
+  {margin-right:0in;
+  margin-left:0in;
+  font-size:12.0pt;
+  font-family:"Times New Roman";
+  }
+p.textintable-western
+  {margin-right:0in;
+  margin-left:0in;
+  font-size:12.0pt;
+  font-family:"Times New Roman";
+  }
+div.Section2
+  {page:Section2;}
+ table.MsoNormalTable
+  {mso-style-parent:"";
+  font-size:10.0pt;
+  font-family:"Times New Roman";
+  }
+span.moz-txt-citetags
+  {}
+-->
+</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)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  <div id="topbara">
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo&nbsp;<a href="/l10n/">l10n</a>&nbsp;&raquo&nbsp;<a href="/l10n/L10N_Framework/">L10N_Framework</a>&nbsp;&raquo&nbsp;<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="0" cellpadding="0" cellspacing="0" width="90%">
+  <!-- MSTableType="layout" -->
+  <tr>
+    <td valign="top">
+    <!-- MSCellType="ContentBody" -->
+    <div class="Section1">
+      <p class="MsoNormal">&nbsp;</p>
+      </div>
+    <p class="MsoNormal" align="center">
+    <font size="6"><b>Localization tips for OpenOffice.org 2.0</b></font><p class="MsoNormal">
+    &nbsp;<p class="MsoNormal">
+    &nbsp;<p class="MsoNormal" align="center">
+      <span style="font-size: 11pt">Javier SOLA - 
+      <a href="http://www.khmeros.info">www.khmeros.info</a> - Last edited
+      <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->05/04/2005<!--webbot bot="Timestamp" i-checksum="12560" endspan --> -
+    <a href="localization_of_openoffice_2.0.html">Top</a></span><p class="MsoNormal">
+    &nbsp;<p class="MsoNormal" align="center" style="text-align: center"><b>
+      <font size="3">This file contains work in progress. </font></b></p>
+      <p class="MsoNormal" align="center" style="text-align: center">
+      <font size="3"><b>The contents of this pages might (and probably 
+      will) change often without warning</b></font></p>
+      <p class="MsoNormal">
+    &nbsp;<p class="MsoNormal">
+    <span style="font-size: 11pt">This page constains information received 
+    in the mailing list or directly from the developers.</span><ul>
+      <li>
+      <p class="MsoNormal"><span style="font-size: 11pt">
+      <a href="#Wizards">Wizard localization</a></span></li>
+      <li>
+      <p class="MsoNormal"><span style="font-size: 11pt">
+      <a href="#Database1">Database Module - Should the field names in the 
+      Database creation wizards be localized</a></span></li>
+      <li>
+      <p class="MsoNormal"><span style="font-size: 11pt"><a href="#Math1">
+      Math Module - Some Strings have localization restrictions</a></span></li>
+      <li>
+      <p class="MsoNormal"><span style="font-size: 11pt"><a href="#sc1">
+      There are lots of strings that look very much like field names in 
+      sc/source/ui/src</a></span></li>
+    </ul>
+    <p class="MsoNormal">&nbsp;<hr color="#0000FF" size="5">
+      <p class="MsoNormal">&nbsp;</p>
+    <p class="MsoNormal"><a name="Wizards"><span style="font-size: 11pt">
+    </span></a><span style="font-size: 11pt; font-weight: 700">Wizard 
+    localization</span></p>
+    <p class="MsoNormal">&nbsp;<p class="MsoNormal">
+    <span style="font-size: 11pt">Warnings:</span><ul>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      You have to be very careful editing wizard template documents, 
+      because if you do something wrong the wizards may crash or do not 
+      work properly. </span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Never open template documents directly by File-&gt;Open. You have to 
+      use File-&gt;Templates-&gt;Edit and navigate to the files and open them, 
+      otherwise you will lose important template document information 
+      (e.g. the description of the template) </span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Do not change the names of template files for the wizards, because 
+      the wizards need some elements of the filenames to work. </span>
+      </li>
+    </ul>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">Some 
+    general important tips on editing the template files for the letter and 
+    the fax wizard (most of this is also true for all other template files):
+    </span>
+    <ul>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Never translate the strings &lt;First Name&gt; &lt;Company&gt; and so on in the 
+      address field. The wizards looks for those strings and the user will 
+      not see them. In most cases strings in &lt;&gt; should not be translated.
+      </span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Never change the name of any of the sections or styles in the 
+      template, the wizard needs the correct english section and style 
+      names. </span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      You have to translate the elements of the templates second page 
+      also. For this you have to somehow force the document to have a 
+      second page (e.g. by a manual page break), translate the strings and 
+      then delete that second page. The document still contains those 
+      texts because they are in the headers. </span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Do only change/translate and not delete any of the placeholders or 
+      user fields in the templates</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Change the page format and all templates language settings (e.g. in 
+      the styles) to the usual ones of the language you translate for
+      </span></li>
+    </ul>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    Unfortunately, there is no possibility to change the font used for the 
+    yellow help windows/boxes. Those windows always use the standard UI font 
+    of your system. On StarOffice this is the installed soui.tff font. I do 
+    not know which font is taken on your system for this if you use 
+    OpenOffice, because OOo is not shipped with a special UI font. The UI 
+    font usage is then handled by the font fallback mechanism in OOo. If 
+    this font does not contain the characters you need you get those little 
+    empty squares - an empty square means that the correct symbol is not in 
+    the font. This may also help you to find out which font is used: The 
+    font used for the yellow boxes is the same as for the menus and dialogs 
+    and so on. </span>
+    <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt">There is no need to translate the dialog 
+    window, that appear when you open a file like bus-elegant_l. If you use 
+    File-&gt;Templates-&gt;Edit you will not get this dialog and the users will 
+    also never see them because the letter wizard template files are opened 
+    by the letter wizard itself. </span>
+    <p class="MsoNormal" align="justify">&nbsp;<hr color="#0000FF" size="5" align="justify">
+      <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt; font-weight: 700"><a name="Database1"></a>
+    Database Module - Should the field names in the Database creation 
+    wizards be localized</span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">I 
+    asked the developer and he says, because we support so many different 
+    databases, please only use a-z characters, no umlauts or hyphens, etc.</span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">Plus 
+    some extra info on these strings: </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    PRJ&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; officecfg</span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    Filename registry\data\org\openoffice\Office\TableWizard.xcu </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">These 
+    strings appear in the Table Wizard in list boxes. </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">No 
+    spaces are allowed because they are field names. </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    <b class="moz-txt-star"><span class="moz-txt-tag">*</span>important<span class="moz-txt-tag">*</span></b>
+    </span></p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">Every 
+    2nd string is a &quot;short name&quot; or short form of the full length string 
+    before it. </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">The 
+    short names <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>cannot 
+    exceed 10 characters<span class="moz-txt-tag">_</span></span> (due to 
+    database restrictions). </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    Therefore the translation cannot exceed 10 characters either. </span>
+    </p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">(For 
+    CJK: You can use 10 double byte Asian characters.) </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify">&nbsp;<hr color="#0000FF" size="5" align="justify">
+      <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt; font-weight: 700"><a name="Math1"></a>Math 
+    Module - Some Strings have localization restrictions</span><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt">Rules regarding the l10n of some of the 
+    strings that have caused bugs in some languages in the past, and may 
+    still be causing problems. </span>
+    <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt">In the math module 66 strings need to 
+    comply to some rules, otherwise some functionality in math is broken.
+    </span>
+    <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt">The 66 strings have some common &quot;Resource 
+    information&quot;:</span><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt">PRJ&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; starmath</span><p class="MsoNormal" align="justify">
+    <span style="font-size: 11pt">Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; source\symbol.src</span></p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    GID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RID_UI_SYMBOL_NAMES</span></p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; itemlist </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">The 
+    strings are names for the greek characters and some extra symbol names.
+    </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">The 
+    rules for this group of 66 strings are: </span></p>
+    <ul>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      The first character has to be an alphabetic character&nbsp; (any 
+      character set allowed).</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      All following characters must be alphanumerical characters (any 
+      character set allowed) or the ASCII decimal dot (a dot from a 
+      different character set or with a different character code is not 
+      allowed).</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      The above rule especially does not allow for spaces or underscore of 
+      any kind to be used. </span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      An ASCII dot should not be followed by another one.</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Case does matter and may be used (That is &quot;alpha&quot; may be used to 
+      denote the lowercase greek character and &quot;ALPHA&quot; for the capitalized 
+      one).</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      No double entries allowed</span></li>
+    </ul>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">A 
+    recommendation for Asian languages is to use the same string as the 
+    english one, since there is no uppercase or lowercase. </span></p>
+    <p class="MsoNormal" align="justify">&nbsp;</p>
+    <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+    Another recommendation is on the use of word separation. In eqch 
+    language only one method should be used. Methods are:</span></p>
+    <ul>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Use no method at all: strictlygreater</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Use one decimal dot: strictly.greater</span></li>
+      <li>
+      <p class="MsoNormal" align="justify"><span style="font-size: 11pt">
+      Use capitalized letters: strictlyGreater</span></li>
+    </ul>
+    <p class="MsoNormal"><span style="font-size: 11pt">Examples:</span></p>
+    <p class="MsoNormal">&nbsp;</p>
+    <p class="MsoNormal"><span style="font-size: 11pt">Good: </span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">-----</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">alpha</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">ALPHA</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">strictly.greater</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">strictlyGreater
+    </span></p>
+    <p class="MsoNormal">&nbsp;</p>
+    <p class="MsoNormal"><span style="font-size: 11pt">Not allowed:</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">------------</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">strictly..greater</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">9trictly</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">strictly_greater</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">strictly greater</span></p>
+    <p class="MsoNormal"><span style="font-size: 11pt">strictly-greater</span></p>
+    <p class="MsoNormal">&nbsp;<hr color="#0000FF" size="5" align="justify">
+      <p class="MsoNormal">&nbsp;</p>
+    <p class="MsoNormal"><span style="font-size: 11pt; font-weight: 700">
+    <a name="sc1"></a>There are lots of strings that look very much like 
+    field names in sc/source/ui/src</span></p>
+    <p align="justify"><b>Q.</b> Besides the wizards in In POTs made from 
+    contents of sc/source/ui/src, there are lots of strings that look very 
+    much like field names (or function names). The whole block of strings 
+    around ~800-~1500 (financial calculations and&nbsp; other functions) 
+    seems to run like this: .1 = function&nbsp;
+    <span class="moz-txt-citetags">&nbsp;</span>description, .even_number = 
+    function (or parameter) name, .odd_number =&nbsp; function (or 
+    parameter) description.</p>
+    <p align="justify">So, I'd like to make sure, what of these is 
+    translatable, and what isn't?</p>
+    <p align="justify"><b>A.</b> All of sc/source/ui/src/scfuncs.src is 
+    translatable, with the exception of the ExtraData structs of course, 
+    which isn't exported to POTs anyway.</p>
+    <p align="justify">You identified the strings of 
+    RID_SC_FUNCTION_DESCRIPTIONS* correctly, first string of a function is 
+    it's description, then alternating follow a parameter's name and it's 
+    description. However, the parameter names should be consistent and 
+    identical for identical functionality, e.g&nbsp; &quot;Database field&quot; for 
+    all parameters that are used as a database field,&nbsp; or &quot;Number&quot; for 
+    any number. Usage could have been defined in the glossary of your 
+    language.&nbsp; What looks like function names in 
+    sc/source/ui/src/globstr.src, for example RID_GLOBSTR.STR_* names SUM, 
+    COUNT and so on, should be identical to the real function names used in 
+    sc/source/core/src/compiler.src for consistency, but isn't necessary for 
+    functionality. These names are offered to the user to choose from in 
+    some dialogs and are mapped to the real functions then.</p>
+    <p align="justify">The function names used in formulas and in the 
+    function pilot are defined in sc/source/core/src/compiler.src and have 
+    the constraints that they can't contain spaces or symbols or other 
+    punctuation characters than dot ('.') or underscore ('_'); letters and 
+    digits are fine (must start with a letter), the definition of letter 
+    here includes accented characters, CJK characters, and so on.</p>
+    <hr color="#0000FF" size="5" align="justify">
+      <p class="MsoNormal">&nbsp;</td>
+  </tr>
+</table>
+
+</div>
+
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/></p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/license.html">Copyright &amp; License</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo2.0_program_translation.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo2.0_program_translation.html (added)
+++ websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo2.0_program_translation.html Mon Dec 19 21:10:54 2011
@@ -0,0 +1,506 @@
+<!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-Language" content="en-us">
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+<title>Localization of OpenOffice 2.0 - Work in Progress</title>
+<style>
+<!--
+p
+  {margin-right:0in;
+  margin-left:0in;
+  font-size:12.0pt;
+  font-family:"Times New Roman";
+  }
+div.Section1
+  {page:Section1;}
+ p.MsoNormal
+  {mso-style-parent:"";
+  margin-bottom:.0001pt;
+  font-size:10.0pt;
+  font-family:"Times New Roman";
+  margin-left:0in; margin-right:0in; margin-top:0in}
+h3
+  {margin-top:12.0pt;
+  margin-right:0in;
+  margin-bottom:3.0pt;
+  margin-left:0in;
+  page-break-after:avoid;
+  font-size:13.0pt;
+  font-family:Arial;
+  font-weight:bold}
+ li.MsoNormal
+  {mso-style-parent:"";
+  margin-bottom:.0001pt;
+  font-size:10.0pt;
+  font-family:"Times New Roman";
+  margin-left:0in; margin-right:0in; margin-top:0in}
+p.tablehead-western
+  {margin-right:0in;
+  margin-left:0in;
+  font-size:12.0pt;
+  font-family:"Times New Roman";
+  }
+p.textintable-western
+  {margin-right:0in;
+  margin-left:0in;
+  font-size:12.0pt;
+  font-family:"Times New Roman";
+  }
+div.Section2
+  {page:Section2;}
+ table.MsoNormalTable
+  {mso-style-parent:"";
+  font-size:10.0pt;
+  font-family:"Times New Roman";
+  }
+span.moz-txt-citetags
+  {}
+-->
+</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)&nbsp;|&nbsp;The Free and Open Productivity Suite</div>
+  </div>
+  <div id="clear"></div>
+  <div id="topbara">
+    <div id="breadcrumbsa"><a href="/">home</a>&nbsp;&raquo&nbsp;<a href="/l10n/">l10n</a>&nbsp;&raquo&nbsp;<a href="/l10n/L10N_Framework/">L10N_Framework</a>&nbsp;&raquo&nbsp;<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="0" cellpadding="0" cellspacing="0" width="90%">
+  <!-- MSTableType="layout" -->
+  <tr>
+    <td valign="top">
+    <!-- MSCellType="ContentBody" -->
+    <div class="Section1">
+      <p class="MsoNormal">&nbsp;</p>
+      <p class="MsoNormal" align="center" style="text-align: center">
+      <font size="5">Translation of the <b>
+      OpenOffice 2.0 </b>program software</font></p>
+      <p class="MsoNormal" align="center" style="text-align: center">&nbsp;</p>
+      </div><blockquote>
+      <p class="MsoNormal"><b><font size="3">Of the OpenOffice software 
+      itself&nbsp; (messages)</font></b><p class="MsoNormal">&nbsp;<p class="MsoNormal" align="justify">
+      <font size="3">The translation of the OpenOffice software 
+      can be easily done using simple specialized translation editors that 
+      are also Open Source. Learning how to use one of these editors 
+      should not take more than half a hour.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+      <font size="3">The translation can be equally done in either the 
+      Linux or the MS Windows environments.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+      <font size="3">The messages that appear different parts of 
+      OpenOffice (menus, screens, error messages) have been extracted from 
+      the source and placed in files that are easy to handle and to 
+      translate. These files are called &quot;PO files&quot; and their format is 
+      used for the translation of many Open Source applications.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+      <font size="3">A PO file is just an structured list of messages that 
+      contains, for each message, the English original message text (msgid) 
+      and the translation to the target language (or an empty string that 
+      will be filled by somebody with the translation of the message). If 
+      the file still does not have any translations (all the translated 
+      string are empty), it is called a PO template file, and usually 
+      given the .POT extension, instead of the traditional .PO extension 
+      of PO files. Once a translator starts to translate a .POT file, he 
+      will save it with the .PO extension. PO are text files in UTF-8 
+      format, so they can also be seen and modified with a normal text 
+      editor that can handle UTF-8 format (most text editors can).</font><p class="MsoNormal">&nbsp;<p class="MsoNormal">
+      <font size="3">But let's start from the beginning, step-by-step.</font><p class="MsoNormal">&nbsp;<p class="MsoNormal">
+      <font size="3">1) You need to know exactly what version of 
+      OpenOffice you want to translate.</font><blockquote>
+        <p class="MsoNormal" align="justify"><font size="3">If you are 
+        not sure about what version to translate, it is always a good 
+        idea to ask in the <a href="mailto:dev@l10n.openoffice.org">
+        dev@l10n.openoffice.org</a> mailing list. Most often you will 
+        translate the latest stable version of the program.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">An exception of this rule is when there is a new 
+        important milestone coming soon, in which case you will have to 
+        translate the upcoming version. For example, at the time this 
+        document is written, version 2.0 of OpenOffice is expected 
+        within the next four to six months, and it is no longer 
+        interesting to attempt translation of a 1.1x version, even if 
+        they are the last stable versions.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">If the inclusion of your language in OpenOffice 
+        requires changes in the code (patches, locale file, etc.), you 
+        will have to work towards the next version that will be released 
+        within the branch that you want to translate. For example, if 
+        the last released version is 2.1, this means that 2.1 is closed 
+        (no changes can be done for 2.1), so you can only work towards 
+        2.2, if the necessary changes are integrated in 2.2. As 2.2 PO 
+        files will probably not be available when you start, you can 
+        always translate the PO files for 2.1, and then, when the PO 
+        files for 2.2 become available, you can upgrade to 2.2 (use the 
+        information stored in the 2.1 PO files to automatically fill the 
+        identical messages in the PO files of 2.2), translate the few 
+        additional messages that there might be in 2.2... and follow the 
+        process explained below.</font></blockquote>
+      <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+      <font size="3">2) Get the POT files and the GSI format file for that 
+      version</font><p class="MsoNormal" align="justify">&nbsp;<blockquote>
+        <p class="MsoNormal" align="justify"><font size="3">The file 
+        that you need for the translation are under:</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <a href="ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/">
+        <font size="3">ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/
+        </font></a>
+        <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">If you point your browser to that address, you 
+        will find a folder for each active branch of OpenOffice (each 
+        active OpenOffice project). Each branch has a name or number: 
+        645 for version 1.1.x of OpenOffice and 680 for 2.x. You should 
+        get the files from the folder that correspond to the version 
+        that you want to localize. If you are working on the latest 
+        branch, you should look into the directory POT. In case of 
+        doubt, ask in the list.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">In whichever directory you look, you will find at 
+        least two files:</font><ul>
+          <li>
+          <p class="MsoNormal" align="justify"><font size="3">A tar 
+          file that contains all the POT files (PO templates)</font></li>
+          <li>
+          <p class="MsoNormal" align="justify"><font size="3">The en-US.sdf 
+          file.</font></li>
+        </ul>
+        <p class="MsoNormal" align="justify"><font size="3">You need to 
+        download both of them. For the moment you do not need the en-US.sdf 
+        file, but you will need it when you finish the translation and 
+        need to convert the PO files to the OpenOffice format. It is 
+        important that - in that process - you use the version of the 
+        en-US.sdf file that is associated to the POT files that you 
+        downloaded. That is why we ask you to download it, label it and 
+        store it now, to avoid confusion later.</font></blockquote>
+      <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+      <font size="3">3) Get a PO file editor, if you do not already have 
+      one.</font><p class="MsoNormal" align="justify">&nbsp;<blockquote>
+        <p class="MsoNormal" align="justify"><font size="3">There are PO 
+        editors for both Linux and Windows, you should use the one that 
+        best fits the working environment of the translators that will 
+        be using the editor.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">In Linux the most used PO editor is probably
+        <a href="http://i18n.kde.org/tools/kbabel/">KBabel</a>, 
+        associated to the KDE user interface (*** REVIEW *** describe 
+        KBabel).</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">In the Windows environment,
+        <a href="poedit.sourceforge.net/">poEdit</a> does the job quite 
+        well. Besides being simple and doing everything that is expected 
+        of a PO file editor, it has its own &quot;translation memory&quot;: each 
+        time a PO file is saved, the editor automatically saves all the 
+        messages of that file and their translations in a database (this 
+        database is your translation memory). When you open a new PO 
+        file (normally this happens when you are upgrading to a new 
+        version), you can ask the editor (just click a button) to search 
+        in the translation memory database for the messages that are in 
+        that PO file, and - if it finds any - to place the translation 
+        in the correct place of the PO file.</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3"><b>poEdit</b> also runs on Linux, and we do 
+        recommend it as a good tool.</font></blockquote>
+      <p class="MsoNormal" align="justify"><font size="3">4) Translate.</font><blockquote>
+        <p class="MsoNormal" align="justify"><font size="3">Translating 
+        the OpenOffice suite is not an easy task. OpenOffice 2.0 contains 
+        roughly 22.000 messages. It is not too far off-the-mark to 
+        consider that it requires a full-time translator for about 12 months 
+        to complete the task, given that he has the right glossary.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">Prior to starting the translation of OpenOffice, 
+        you should have a glossary of computer terms (user-interface 
+        terms) for the target language, otherwise you will be stopping all 
+        the time to figure out specific translations for different 
+        terms, and your translation will be inconsistent, specially if 
+        it is done by several translators working together (which is a 
+        good idea). Besides your computer terminology glossary, you will 
+        also need mathematical, statistical and accounting 
+        terminologies, to translate many names of functions used by 
+        Calc.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">You should consider (depending on your 
+        resources), how many translators you want to assign to the task 
+        of translating the OpenOffice software. This will depend on the 
+        overall task that you set for yourself. Will you also translate 
+        the help? Will you translate documentation? Training materials? 
+        You should also consider how long you want your translation to 
+        take.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">In our experience, in the case of translation 
+        being done professionally, a team of three or four 
+        translators can work very well, having each team member 
+        translate his part and double-check translations made by another 
+        team member. With a three person team translation of the 
+        software can be accomplished in four months (of course it can be 
+        three or five, depending on speed, enthusiasm and the quality of 
+        the glossary, but&nbsp; four is a good reference to start with).</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">You should also develop translation guidelines 
+        for translators, regarding length of messages, how you should 
+        translate certain things, how to deal with variables, etc. </font>
+        <p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">Variable names in OpenOffice have several 
+        different ways of being represented. As far as we know, 
+        variables might take one of these forms:</font><pre wrap>&amp;VariableName;
+%VariableName%
+%VariableName
+$VariableName$
+$(VariableName)
+${VariableName}
+($VariableName)
+#VariableName#
+$[VariableName]</pre>
+        <p class="MsoNormal" align="justify">
+        <font size="3">Variables are place-holders for dynamic 
+        information (the name of a file, a program, some name) to which 
+        the message you are translating makes reference. The Variable 
+        should always be in the translated sentence in the right place 
+        for that information. <b>You should never translate the name of 
+        a variable</b>. </font>
+        <p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">&nbsp;</blockquote>
+      <p class="MsoNormal" align="justify"><font size="3">5) Installation 
+      of <b>Translate Toolkit</b></font><blockquote>
+        <p class="MsoNormal" align="justify"><font size="3">It is now 
+        time to install the <b>Translate Toolkit </b>in your 
+        computer (either Linux or Windows). These tools are used to 
+        check your messages and to convert your PO files pack to a 
+        format that is clearly understood by the OpenOffice software.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">(*** REVIEW *** installation of Translate 
+        Toolkit)</font></blockquote>
+      <p class="MsoNormal" align="justify"><font size="3">6) Check your PO 
+      files</font><blockquote>
+        <p class="MsoNormal" align="justify"><font size="3">Once you 
+        have finished translating and made a back-up copy of your PO files, it is a good idea to 
+        check if the are correct is some technical aspects, such as 
+        making sure that if a given variable is in the original string, 
+        the same variable is also in the translation, or that if some 
+        message starts or finishes with a blank space, so that the 
+        translation, having similar capitalizations in original and 
+        translation (for scripts that have capital letters), etc...</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">The checking process consists on checking your 
+        translated PO files for inconsistencies or possible problems, 
+        filter to new files all the problematic translations, work on 
+        them, and then merge them back into the original files. As 
+        complicated as this might sound, it is quite simple, by using 
+        the Translate Toolkit.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">a) Filtering</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">The tool from the Translate Project that does 
+        this check is called <b>POFILTER</b>, and it should be used from 
+        the console (Linux) or from the command prompt (Windows). We 
+        assume that you have followed the instructions in the prior 
+        section and that the PO tools correctly installed in your 
+        computer.</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">POFILTER analyses a whole tree of PO files, 
+        searching for possible errors and problems in the PO files one 
+        by one. It creates as output another tree, identical in 
+        structure to the tree in which your PO files are, and in this 
+        new tree, in the same place that the original PO files in the 
+        first tree, it creates PO files in which only problematic 
+        messages are included. For example:</font></p>
+        <ul>
+          <li>
+          <p class="MsoNormal" align="justify"><font size="3">If in 
+          your PO file tree you have a file called po/sfx2/source/menu.po, 
+          and that file has a problem in one of the message.</font></li>
+          <li>
+          <p class="MsoNormal" align="justify"><font size="3">And you 
+          run POFILTER, specifying &quot;checks&quot; are your output tree.</font></li>
+          <li>
+          <p class="MsoNormal" align="justify"><font size="3">A file 
+          with path checks/sfx2/source/menu.po will be created, which 
+          will include only messages from the file po/sfx2/source/menu.po 
+          which POFILTER considers that you should check again by 
+          hand.</font></li>
+        </ul>
+        <p class="MsoNormal" align="justify"><font size="3">In order to 
+        run POFILTER, you should use in the command line the following 
+        syntax:</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">pofilter --openoffice &lt;your-po-file-tree&gt; 
+        &lt;tree-where-checks-will-be-stored&gt;</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">Of course, we assume that the <b>pofilter</b> 
+        program is in your path or that you write the whole path for it. 
+        For example, as in the case above, all your files are in a 
+        directory called <b>po</b>, and you want the output to go to a 
+        directory called <b>checks</b>, and (for this particular 
+        example) we assume that you are working on Windows and that your 
+        Translate Project tools are in the \dev\tools\ directory, you 
+        should use the command:</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">\dev\tools\pofilter&nbsp; --openoffice&nbsp; po&nbsp; 
+        checks</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">Sometimes - depending on your language - POFILTER 
+        can give you a lot of false positives (find as possible errors 
+        translations that are correct). POFILTER, for example checks by 
+        default if capitalization in the original and in the translation 
+        is similar. This - of course - does not apply to Indic 
+        languages, which have no capital letters. Also, by default, 
+        POFILTER checks if all messages have been translated. In some 
+        cases you might do test or partial transaltions, so you do want 
+        this test deactivated. </font>
+        <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">IT is possible to indicate to POFILTER which test 
+        you want to deactivate when using it. The most useful tests that POFILTER 
+        uses are:</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+·<span style="font-style:normal; font-variant:normal; font-weight:normal; font-family:Times New Roman"><font size="3">&nbsp;&nbsp;&nbsp;&nbsp;
+</font>
+</span>escapes&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Checks 
+whether escaping is consistent between the two strings</p>
+<p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+·&nbsp;&nbsp;&nbsp;&nbsp;
+endpunc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Checks 
+whether punctuation at the end of the strings match</p>
+<p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+·<span style="font-style:normal; font-variant:normal; font-weight:normal; font-family:Times New Roman"><font size="3">&nbsp;&nbsp;&nbsp;&nbsp;
+</font>
+</span>unchanged&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Checks 
+whether a translation is basically identical to the original string</p>
+<p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+·<span style="font-style:normal; font-variant:normal; font-weight:normal; font-family:Times New Roman"><font size="3">&nbsp;&nbsp;&nbsp;&nbsp;
+</font>
+</span>untranslated&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Checks 
+whether a string has been translated at all</p>
+<p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+·<span style="font-style:normal; font-variant:normal; font-weight:normal; font-family:Times New Roman"><font size="3">&nbsp;&nbsp;&nbsp;&nbsp;
+</font>
+</span>variables&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Checks 
+whether variables of various forms are consistent between the two strings</p>
+<p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+·<span style="font-style:normal; font-variant:normal; font-weight:normal; font-family:Times New Roman"><font size="3">&nbsp;&nbsp;&nbsp;&nbsp;
+</font>
+</span>whitespace&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Checks 
+whether white spaces at the beginning and end of the strings match</p>
+        <p class="MsoPlainText" style="text-indent: -127.0pt; margin-left: 145.0pt; margin-top:0; margin-bottom:0">
+&nbsp;</p>
+        <p style="margin-left: 0; margin-top:0; margin-bottom:0" align="left">
+To see a complete list of tests, please run <b>pofilter</b> with the -l option, 
+or go to the <a href="translate.html">Translate Project Reference Documentation</a>.</p>
+        <p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">The excludefilter option is used in the command 
+        line to exclude specific filter(s). As an example, if you want 
+        to run POFILTER while deactivating the capitalization check and 
+        the check for untranslated (empty or identical to the original), 
+        you should use the command (following with the same example):</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">\dev\tools\pofilter --openoffice --excludefilter=untranslated 
+      --excludefilter=unchanged --excludefilters=simplecaps po checks</font><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <b><font size="3">b) Correct</font></b><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">Once you run POFILTER, you need to use your PO 
+        editor to check all the files that are in the <b>checks</b> 
+        directory, until you are sure that they are all correct.</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <b><font size="3">c) Merge corrected messages back.</font></b><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">The next step is re-integrate the corrections in 
+        the original PO files. This is done with the Translate Tool 
+        program POMERGE. Before you do it, we recommend that you make a 
+        new back-up copy of your <b>po</b> and <b>checks</b> 
+        directories, then you can run:</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">pomerge -i &lt;folder-with-corrected-files&gt; -t 
+        &lt;folder-with-original-incorrect-po-files&gt; -o 
+        &lt;folder-for-corrected-files&gt;</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">If we use that we have been following, and we 
+        want to just over-write the incorrect files in the <b>po</b> 
+        folder with corrected files, we should use the command:</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">\dev\tools\pomerge -i checks -t po -o po</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">At this point you can just go ahead, or run again
+        <b>pofilter</b>, to see if all the problems that you had 
+        detected have disappeared. If pofilter gives new positives, you 
+        have to repeat the whole checking process again.</font><p class="MsoNormal" align="justify">
+        &nbsp;</blockquote>
+      <p class="MsoNormal" align="justify"><font size="3">7) Create an 
+      OpenOffice file that contains your translations</font><blockquote>
+        <p class="MsoNormal" align="justify">
+        <font size="3">Now the files are ready to be converted back to a 
+        format that OOo likes. You can do this conversion using the <b>
+        po2oo</b> tool from Translate Project . For this you need to 
+        remember were you put the original en-US.sdf file that you 
+        downloaded together with the PO files, because you need to 
+        include the path to it in the po2oo command. </font>
+        <p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">In order to create, an OpenOffice file, you also 
+        need to indicate what will the the locale for the transaltion 
+        you are doing. You must include in the command the name fo the 
+        locale for which you are translating.</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">po2oo -i &lt;folder-with-po-files&gt; -t en-US.sdf -o 
+        &lt;name-of-GSI-format-file&gt; -l &lt;Locale-name&gt;</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">In our example, as we are translating for Khmer, this could look like:</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">\dev\tools\po2oo -i po -t en-US.sdf -o 
+        oo-2.0-km-GSI.sdf -l km</font><p class="MsoNormal" align="justify">
+        &nbsp;<p class="MsoNormal" align="justify">
+        <font size="3">which would produce as output the file <b>
+        oo-2.0-km-GSI.sdf</b>, the final product for which you have been 
+        working for all this time, and which will be integrated in the 
+        sources of OpenOffice.</font><p class="MsoNormal" align="justify">
+        &nbsp;</blockquote>
+      <p class="MsoNormal" align="justify"><font size="3">8) Create an 
+      issue in OpenOffice</font><p class="MsoNormal" align="justify">&nbsp;<blockquote>
+        <p class="MsoNormal" align="justify">
+        <span style="font-size: 11.0pt">Create an issue for the 
+        Localization (L10n) project. To submit 
+      an issue you first need to login into the OpenOffice website, then 
+      hit <b>File Issue</b> on the left hand 
+      menu… go to <b>proceed</b> in the next page… click in the component<b> 
+      l10n</b> in the next one… are you are ready to file it. Select 
+      version <b>current</b>, subcomponent <b>code</b>, type ENHANCEMENT, 
+      Summary <b>GSI file for language…., </b>and hit<b> Submit.
+      </b>The system will ask you if you want to attach a file and what 
+      type<b>. </b>Attach the </span><font size="3">oo-2.0-km-GSI.sdf file 
+        (or whatever you have called it) </font>
+        <span style="font-size: 11.0pt">&nbsp;and<b>… submit it. </b>You are done.</span><p class="MsoNormal" align="justify">&nbsp;<p class="MsoNormal" align="justify">&nbsp;</blockquote>
+    </blockquote>
+    </td>
+  </tr>
+</table>
+
+</div>
+
+
+
+  </div>
+
+  <div id="footera">
+    <div id="poweredbya">
+      <p><img src="/images/feather-small.gif"/></p>
+    </div>
+    <div id="copyrighta">
+      <p>
+	Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+	Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+	decision making process	have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+	not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+	yet to be fully endorsed by the ASF.</p>
+      <p>
+	<a href="/license.html">Copyright &amp; License</a>
+	<br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+	OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+	Other names appearing on the site may be trademarks of their respective owners.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo_images/image001.jpg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo_images/image001.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo_images/imageCVS2.jpg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/ooo-site/trunk/content/l10n/L10N_Framework/ooo20/oo_images/imageCVS2.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream



Mime
View raw message