Howto
Here is how to get set up for translation work. It is assumed here that you already
know your way around gettext message catalogs. If you're new to this, read the chapter
on NLS in the PostgreSQL Documentation.
-
To continue an existing translation, download a new PO file by following the
links in the status tables. Fill in the file as much
as you want.
-
To start a new translation, download a POT file by clicking on one of the
catalog names in the left column of the status
tables. First, fill in all the fields in the header and remove the fuzzy
flag. Particularly, the character set information is very important and must
not be left out! Then fill in the rest of the file as much as you want.
-
When you are done editing, check the
file for errors. If you're using the Emacs PO mode, press V. From the command line, run msgfmt -o /dev/null -v -c yourfile.po. Or copy the file
into the main PostgreSQL source tree and run gmake
maintainer-check-po. If you don't do this, your file might contain bugs
that cause program crashes, which will quickly disenchant users from PostgreSQL
and internationalized software in general.
-
Submit the resulting file to the Patch Tracker. Please do not send patches; send the whole file. If
you're concerned that the file is too big, run it through a compression
program. Also, please send each PO file as a separate attachment; no tar or zip
archives please. Both of these rules make it easier for the person installing
your files.
Please don't edit the PO files with a plain text editor. You're making your life
unnecessarily hard. There are several tools that make editing PO files really
easy.
-
GNU Emacs and XEmacs have PO editing modes.
-
KBabel is for those who like KDE-based tools.
-
poEdit is yet another tool, which even works under Windows
Check out the home of the GNU Translation
Project. There you can find out about mailing lists, web sites, and other
resources for translation efforts to your language. Some of these resources are
GNU-oriented, but others are not.
|
