diff README4TRANSLATORS @ 69:86f1f7f6d332

i18n first draft - gettext support added in SàT - first draft of french translation - added README with a HOWTO for translators
author Goffi <goffi@goffi.org>
date Wed, 03 Mar 2010 17:12:23 +1100
parents
children 86d249b6d9b7
line wrap: on
line diff
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README4TRANSLATORS	Wed Mar 03 17:12:23 2010 +1100
@@ -0,0 +1,25 @@
+First of all, thank you for helping translating SàT :)
+
+To translate a file, you can use a dedicated tool as the excellent gtranslator:
+- use the template .po file (e.g. sat.po) and name it to your translated language (e.g. fr.po for french); you can preferably generate a new template directly from the source with the following command (eventually adapted):
+> xgettext -L python -d sat sat.tac tools/*py plugins/*py
+
+- use the choosed tool (a simple text editor can be sufficient) to edit the file: e.g. gtranslator fr.po
+
+- once you translation is finished (or partly finished: the english sentences are used if there is no translation), you can test them by generating a binary and moving it to the right place with the following commands:
+> msgfmt -o sat.mo fr
+> mv sat.mo i18n/fr/LC_MESSAGES/sat.mo
+
+/!\ Note that you don't need to precise the file extention mith the msgfmt command, here fr mean "use fr.po file"
+
+- if you have already a translation, and want to update it (new translations to do, some sentences have changed), you can use the following commands:
+> msgmerge fr.po sat.po > fr2.po
+and if everything is allright
+> mv fr2.po fr.po
+
+Don't forget that you can use the version-control system (mercurial, the "hg" command) to keep history of you translations.
+
+You can check the fr.po file to see how it's done and to know what to put while you set up you translation tool.
+
+Trank you again for you help, don't forget to give me your name and contact mail so I can credit you, and don't hesitate to contact me if you need help (goffi@goffi.org).
+