From AbiWiki

Revision as of 03:50, 24 November 2010

Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page

Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page

<h2>Update an Existing AbiWord Translation</h2>

<p>These instructions will allow you to update an existing AbiWord translation.</p>

<h3>Step 1: Getting a Translation</h3>

<p>First, you need to download a <b>PO</b> file containing the translation for your language. Look for the appropriate file from the translation status table on the right. These PO files appear in the form <strong><em>xx-YY</em>.po</strong> where <em><strong>xx</strong></em> or <em><strong>xxx</strong></em> is your ISO language code and <em><strong>YY</strong></em> is your ISO country code. For example, fr-FR is French and pt-BR is Brazilian Portuguese. (If you don't know the ISO code for your language, look here and see this list of ISO county codes.)</p>

<h3>Step 2: Translate xx-YY.po</h3>

<p>Each phrase to translate in the file <strong><em>xx-YY</em>.po</strong> will appear in this format:</p>

<blockquote><code>

   WHITE-SPACE<br />
   #  TRANSLATOR-COMMENTS<br />
   #. AUTOMATIC-COMMENTS<br />
   #: REFERENCE...<br />
   #, FLAG...<br />
   msgid UNTRANSLATED-STRING<br />
   msgstr TRANSLATED-STRING

</code></blockquote>

<p>The important elements are the <b>msgid</b> which contains the orignal phrase in English and the <b>msgstr</b> which contains the translated phrase. Look for <b>msgstr</b>'s which haven't been translated. They will contain an empty string <b>""</b>.</p>

<p>For example, if you are translating the msgid "Cancel" into Spanish, you would only need to change "" to the Spanish word "Cancelar".</p>

<p>From this:</p>

<blockquote><code>

#. DLG_Cancel<br />
#: po/tmp/xap_String_Id.h.h:127<br />
msgid "Cancel"<br />
msgstr ""<br />

</code></blockquote>

<p>To this:</p>

<blockquote><code>

#. DLG_Cancel<br />
#: po/tmp/xap_String_Id.h.h:127<br />
msgid "Cancel"<br />
msgstr "Cancelar"<br />

</code></blockquote>

<p>In addition to empty strings "", look for strings which are marked with the "fuzzy" flag:</p> <blockquote><code>

#, fuzzy 

</code></blockquote>

<p>When the original msgid strings are changed in the AbiWord source code, the translation is marked as "fuzzy", so you may have to retranslate these phrases. After you retranslate the phrase, remove the fuzzy flag so the next translator will know that the translation is no longer out of date.</p> <p>If you are unsure how to translate a string, it is good idea to mark it with a "fuzzy" flag and leave a comment for the next translator to check it. For instance if you don't know whether to translate "Cancel" as "Cancelar" or "Anular", you could change the entry to:</p> <blockquote><code>

#  Should it be "Cancelar" or "Anular"?<br />
#. DLG_Cancel<br />
#: po/tmp/xap_String_Id.h.h:127<br />
#, fuzzy<br />
msgid "Cancel"<br />
msgstr "Cancelar"<br />

</code></blockquote>

<p>Strings which contain a <strong>"&"</strong> or <strong>"&"</strong> can be accessed with a key press in a menu or a dialog box. The character following the <strong>&</strong> or

<strong>"&"</strong> will be underlined to tell the user which key to press.</p>

<p>For example, the menu item "&Header" would appear as "<u>H</u>eader" and can be reached by pressing <b>H</b> or <b>Alt + H</b>. The Spanish translation of "Header" is "Cabecera", so the strings would look like this:</p>

<blockquote><code> msgid "&Header"<br /> msgstr "&Cabecera" </code></blockquote>

<p>Only underline one character per menu item and avoid choosing thin characters such as 'i' or 'l' because it will be difficult for the AbiWord user to see that these characters are underlined. Also avoid underlining characters such as 'j' and 'y' whose strokes are lower than normal letters and difficult to read when underlined.</p>

<p>Long strings that are difficult to read can be broken into multiple lines by enclosed extra lines in double quotation marks. Breaking the string into multiple lines will have no effect on the final string, since the computer will strip away any spaces and hard returns outside of the quotation marks. </p>

<p>If you want to put double quotation marks inside a string, use the escape code <b>\"</b>   The escape code <b>\n</b> adds a hard return to a string and <b>\t</b> adds a tab. As a general rule, only add these escape codes to the <b>msgstr</b> if they are found in the <b>msgid</b>. If you see <b>%s</b> or <b>%d</b> in the <b>msgid</b>, that indicates that a string variable or a numerical variable will be inserted into the string at that point. Make sure that the <b>msgstr</b> contains the same number of these variables as are found in the <b>msgid</b>.</p>

<p>For instance, here is a good example of a screen message with a number of escape codes and variable codes. Notice how it is broken up over several lines to make it easier to read and each line is enclosed in double quotation marks:</p>

<blockquote><code> msgid ""<br /> "%s not implemented yet.\n\n"<br /> "If you are a programmer, feel free to add code in %s, line %d\n"<br /> "and mail patches to:\n\n"<br /> "\tabiword-dev@abisource.com\n\n"<br /> "Otherwise, please be patient."<br /> msgstr ""<br /> "%s todaví­a no está implementado.\n\n"<br /> "Si usted es un programador, siéntase libre para añadir código en %s, lí­nea %d\n"<br /> "y enviar parches a:\n\n"<br /> "\tabiword-dev@abisource.com\n\n"<br /> "En otro caso, tenga paciencia." </code></blockquote>

<p>You can edit the file <b><i>xx-YY</i>.po</b> with any text editor so long as you save it in the same character encoding listed in the PO header. It is recommended to use UTF-8 (8-bit Unicode) encoding. To avoid syntax errors, use a text editor that recognizes source code such as emacs, vim, gedit, or kate so that you can see when you improperly terminated a string or forgot to enclose it in double quotation marks. Notepad++ is a good text editor for Windows users. (Set "Language" to "C" and mark "Encode in UTF-8" under "Format").</p>

<p>Some people prefer to use special translation software such as KBabel or poedit.

which has translation memory so you only have to translate a phrase once. These programs also help you maintain a consistent translation for every instance of a word. If multiple people will be working on the translation, it may be easier to use a web-based PO translator such as Pootle.</p>

<h3>Step 3: Check the Translation</h3>

<p>After you have finished your translation, you may want to check how it will appear in AbiWord. Follow these instructions to download the <b>abi</b> module with CVS, and use the <b>ui-backport.pl</b> script to convert your <b><i>xx-YY</i>.po</b> file to <b><i>xx-YY</i>.po</b> Replace the <b><i>xx-YY</i>.strings</b> file in your current installation of AbiWord with the <b><i>xx-YY</i>.strings</b> file that you just created and then run AbiWord. For more information see New AbiWord Translation.</p>

<h3>Step 4: Submit the Translation</h3>

<p>After you have translated and tested your translation, please send your xx-YY.po file to the developer's mailing list so that we can incorporate your translation into the project. Please zip the attachment before sending it, as that will be more convenient for users on slow internet connections, and to prevent it from being marked as spam my our mail server.</p>

<p>You can subscribe to the mailing list by sending an email to abiword-dev-request@abisource.com with the word "subscribe" in the message body. Once you're subscribed, you can send an email to abiword-dev@abisource.com and attach your translation. Please zip or gzip your attachment before sending it, otherwise it might be too large or marked as spam. </p>