comparison README4TRANSLATORS @ 1367:f71a0fc26886

merged branch frontends_multi_profiles
author Goffi <goffi@goffi.org>
date Wed, 18 Mar 2015 10:52:28 +0100
parents 0db0013c59dd
children 5e72efd2f95d
comparison
equal deleted inserted replaced
1295:1e3b1f9ad6e2 1367:f71a0fc26886
3 NOTE: *.po files are in i18n directory 3 NOTE: *.po files are in i18n directory
4 4
5 To translate a file, you can use a dedicated tool as the excellent gtranslator: 5 To translate a file, you can use a dedicated tool as the excellent gtranslator:
6 6
7 - 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, the following command use zsh's globbing syntax), launched from root sat dir after having emptied the build directory: 7 - 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, the following command use zsh's globbing syntax), launched from root sat dir after having emptied the build directory:
8 > xgettext -L python -d sat --keyword=D_ -p i18n **/*(.py|.tac|primitivus|wix)(.) **/jp(.) 8 > xgettext -L python -d sat --keyword=D_ -p i18n **/*(.py|.tac|primitivus)(.) **/jp(.)
9 9
10 - then to start a new translation, copy i18n/sat.po to your language file, e.g. cd i18n; cp sat.po fr.po 10 - then to start a new translation, copy i18n/sat.po to your language file, e.g. cd i18n; cp sat.po fr.po
11 11
12 - use the choosed tool (a simple text editor can be sufficient) to edit the file: e.g. gtranslator fr.po 12 - use the choosed tool (a simple text editor can be sufficient) to edit the file: e.g. gtranslator fr.po
13 13