/update.pl --pot
mv abiword.pot zz-ZZ.po
(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.
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8-bit\n"
msgid "the dictionary"
msgstr "grompabikku-la"
(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:
msgstr ""
"implog revulam"
"groppsigu moturo nula"
Later processing steps will automatically divide long lines for you in any case.
msgfmt -cv zz-ZZ.po
Fix any errors that msgfmt finds. Then run this script:
./ui-backport.pl zz-ZZ
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.
./update.pl zz-ZZ
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.
LANG=zz-ZZ.utf8
LC_ALL=zz_ZZ
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.
.gtkrc-2.0
In that file, place a line saying
gtk-font-name = "sans 20"
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.
./update.pl --pot
mv abiword.pot zz_ZZ.po
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.
make zz_ZZ.gmo
make install (you may need privilege)
locale -a
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.
cd /usr/share/i18n/locales/
[pick any language that seems similar to Pelonian, such as en_GB]
cp en_GB zz_ZZ
[edit zz_ZZ as needed, or just leave it the way it is]
localedef -i zz_ZZ -c -f UTF-8 zz_ZZ
[for older versions of localedef]
localedef -c -f UTF-8 \
-i zz_ZZ /usr/share/locale/zz_ZZ
localedef --add-to-archive /usr/share/locale/zz_ZZ
[for newer versions]