Chip 2004 March

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2004 March / Chip_2004-03_cd1.bin / software / abi / abiword.exe / AbiWord / howtotranslation.html < prev next >

Wrap

Extensible Markup Language | 2004-01-20 | 17.4 KB | 130 lines

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head>  <meta http-equiv="content-type" content="text/html; charset=UTF-8" /> <title>Translating AbiWord</title> <link href="../style.css" rel="stylesheet" type="text/css" /> </head> <body> <div class="banner"> <a href="../index.html" class="bars">Home</a> > <a href="index.html" class="bars">How To</a> > Translation </div> <div class="main"> <h1>Translating AbiWord</h1> <h2>Getting started</h2> <ol> <li dir="ltr" style="text-align: left"> If you want to work on a particular language, say Pelonian (language zz-ZZ), you may start this way:</li> </ol> <pre class="Plain_Text"> /update.pl --pot</pre> <pre class="Plain_Text"> mv abiword.pot zz-ZZ.po</pre> (The .po suffix doesn't mean Pelonian; it applies to any language.) Now edit zz-ZZ.po. Fix the comment at the start to indicate who you are, what the language is, and when you are doing this work. <ol> <li dir="ltr" style="text-align: left"> I strongly recommend you use Unicode UTF-8 to encode all your Pelonian strings. In the comment at the top of zz-ZZ.po, make sure the following two lines appear:</li> </ol> <pre class="Plain_Text"> "Content-Type: text/plain; charset=UTF-8\n"</pre> <pre class="Plain_Text"> "Content-Transfer-Encoding: 8-bit\n"</pre> <ol> <li dir="ltr" style="text-align: left"> Now you want to translate all lines that start with msgid and place the translation in place of the empty string in the following msgstr line. For instance, you might translate</li> </ol> <pre class="Plain_Text"> msgid "the dictionary"</pre> <pre class="Plain_Text"> msgstr "grompabikku-la"</pre> (Sorry, my knowledge of the Pelonian language is limited.) Translate as many entries as you like. Entries that have %d or %s should most likely be translated with %d and %s in place, referring to numeric or string data to be filled in later. Don't worry that lines get very long. If you like, you may divide long lines: <pre class="Plain_Text"> msgstr ""</pre> <pre class="Plain_Text"> "implog revulam"</pre> <pre class="Plain_Text"> "groppsigu moturo nula"</pre> Later processing steps will automatically divide long lines for you in any case. <ol> <li dir="ltr" style="text-align: left"> Once you have translated as much as you want, check your translation for sanity:</li> </ol> <pre class="Plain_Text"> msgfmt -cv zz-ZZ.po </pre> Fix any errors that msgfmt finds. Then run this script: <pre class="Plain_Text"> ./ui-backport.pl zz-ZZ</pre> This program places strings in ../user/wp/strings/zz-ZZ.strings. The next time you build AbiWord, the Pelonian strings will be available, or you can manually copy the strings file to $prefix/AbiSuite-2.0/AbiWord/strings/zz-ZZ.strings and see them immediately when you next run AbiWord. <ol> <li dir="ltr" style="text-align: left"> Later, you will want to fix your translations, finish strings you didn't translate earlier, and see if new strings have been introduced into AbiWord that you need to translate. Run this script:</li> </ol> <pre class="Plain_Text"> ./update.pl zz-ZZ</pre> You will be see a summary that tells you how many messages have been translated and how many are still untranslated. It will also indicate how many "fuzzy" translations there are. These are translations that you have made but which may no longer be right, because AbiWord no longer uses quite the same text in the message that it did when you first made the translation. Search for the word "fuzzy" in zz-ZZ.po, and fix all such translations, if necessary. Remove the line that says "fuzzy" to indicate that you have fixed them. Then do whatever other translations you want, and backport as indicated above. <ol> <li dir="ltr" style="text-align: left"> There are several alternative techniques for building Pelonian string files, although I don't recommend them.</li> <ol> <li dir="ltr" style="text-align: left"> Look in <a href="http://www.abisource.com/dev/strings/strings.html">http://www.abisource.com/dev/strings/strings.html</a> (quite long; all you need is the beginning) to find a fairly complete translation of some language that you can work from, perhaps because the language is related to Pelonian. Say you choose no-NO. Copy user/wp/strings/no-NO.strings to user/wp/strings/zz-ZZ.strings and modify the translations. Disadvantages: (a) You can't easily keep up with new strings added to AbiWord over time, (b) You can't easily find which Pelonian strings you haven't done yet, (c) In the cases where the same English string occurs in multiple instances, you need to introduce your Pelonian translation for each instance. (d) You have to trust the no-NO translation, which is one step removed from the English source.</li> <li dir="ltr" style="text-align: left"> Run AbiWord --dumpstrings; you will find a fresh file in the current directory called en-US.strings. Copy this file to user/wp/strings/zz-ZZ.strings and edit it. Disadvantages: (a-c) above.</li> </ol> </ol> <h2>Unix and Gtk+ issues</h2> <ol> <li dir="ltr" style="text-align: left"> In order for your translations to appear, you need to set your environment to specify your language. Before you start AbiWord, set your LANG and LC_ALL environment variables to </li> </ol> <pre class="Plain_Text"> LANG=zz-ZZ.utf8</pre> <pre class="Plain_Text"> LC_ALL=zz_ZZ</pre> AbiWord uses the LANG variable; Gtk+ uses the LC_ALL variable. When you run AbiWord, you should see all the strings you have translated in Pelonian, not in English. <ol> <li dir="ltr" style="text-align: left"> You might not like the font in which Pelonian is displayed. In your home directory, place a file called</li> </ol> <pre class="Plain_Text"> .gtkrc-2.0</pre> In that file, place a line saying <pre class="Plain_Text"> gtk-font-name = "sans 20"</pre> The 20 is a size indicator; you may change that if you like. Now you must tell Pango (which actually draws the fonts) what you mean by sans 20. Copy /usr/local/etc/pango/pangox.aliases (it may be in a different place, such as /etc/pango) to ~/.pangox_aliases). Add your favorite Pelonian font (mine is -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1) to the top of the entry for "sans normal normal normal normal". You may have to remove other fonts from that list if you don't get the font you want. If your favorite font is monospace (like mine), set your gtk-font-name to "monospace 20" and put your font name in the entry for "monospace normal normal normal normal". If you don't see any font at all, your Unix machine is most likely using the fontconfig library. Look at its configuration file in /etc/fonts/fonts.conf to see where it finds fonts. For instance, you might find that it mentions the directory /usr/share/fonts, which is a good place to put extra fonts, such as Unicode TrueType fonts. Apparently /usr/share/fonts must not be a symlink to a remotely mounted filesystem. <ol> <li dir="ltr" style="text-align: left"> Your AbiWord translations only apply to those menus and buttons that AbiWord builds for itself. AbiWord also uses "stock" items from Gtk+, including buttons that say "Cancel" and "OK". If you don't see these messages in Pelonian, you need to introduce Pelonian strings to the gtk+ library. Get the source distribution of gtk+ (mine is gtk+-2.0.0 as of 2/2003). In the po subdirectory, run</li> </ol> <pre class="Plain_Text"> ./update.pl --pot</pre> <pre class="Plain_Text"> mv abiword.pot zz_ZZ.po</pre> and edit the zz_ZZ.po file just as you did for Abiword, paying special attention to those items labeled with gtk/gtkstock.c. Modify the Makefile, adding zz_ZZ.po and zz_ZZ.gmo everywhere you see zh_CN.po. <pre class="Plain_Text"> make zz_ZZ.gmo</pre> make install (you may need privilege) <ol> <li dir="ltr" style="text-align: left"> If you get the error message that your zz_ZZ locale isn't recognized, or you don't see stock items in Pelonian, try</li> </ol> <pre class="Plain_Text"> locale -a</pre> If zz_ZZ is not listed, you need to set up Pelonian as one of the supported locales on your machine. You will need privilege, typically as root. <pre class="Plain_Text"> cd /usr/share/i18n/locales/</pre> [pick any language that seems similar to Pelonian, such as en_GB] <pre class="Plain_Text"> cp en_GB zz_ZZ</pre> [edit zz_ZZ as needed, or just leave it the way it is] <pre class="Plain_Text"> localedef -i zz_ZZ -c -f UTF-8 zz_ZZ</pre> [for older versions of localedef] <pre class="Plain_Text"> localedef -c -f UTF-8 \</pre> <pre class="Plain_Text">-i zz_ZZ /usr/share/locale/zz_ZZ</pre> <pre class="Plain_Text"> localedef --add-to-archive /usr/share/locale/zz_ZZ</pre> [for newer versions] <ol> <li dir="ltr" style="text-align: left"> If Pelonian is written right-to-left (RTL) instead of LTR, you might need to put a directional marker such as u202b at the start of any message that includes non-RTL characters, such as periods, query marks, and numbers. But a better solution is to set the translation for the Gtk (not AbiWord) msgid "default:LTR" to be msgstr "default:RTL". This single setting modifies the "outer" directionality, influencing the position of widgets within containers and the default direction of all text.</li> </ol> </div> <div class="index"> <a href="../index.html" class="bars">Top Page</a> <a href="../tutorial/index.html" class="bars">Tutorial</a> <a href="../howto/index.html" class="bars">How To</a> <a href="../info/index.html" class="bars">Information</a> <a href="../interface/index.html" class="bars">Interface</a> <a href="../plugins/index.html" class="bars">Plug-ins</a> <a href="../problems/index.html" class="bars">Problems</a> <a href="../credits.html" class="bars">Credits</a> <a href="../azindex.html" class="bars">Index</a> <a href="../fdl.html" class="bars">GNU FDL</a> </div> </body> </html>