Mercurial > libervia-backend
comparison README4TRANSLATORS @ 2954:5e72efd2f95d
doc: minor fixes + use ".pot" extension instead of ".po" for template in README4TRANSLATORS
author | Goffi <goffi@goffi.org> |
---|---|
date | Sun, 26 May 2019 22:21:56 +0200 (2019-05-26) |
parents | 0db0013c59dd |
children |
comparison
equal
deleted
inserted
replaced
2953:3caf460bc125 | 2954:5e72efd2f95d |
---|---|
2 | 2 |
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 .pot file (e.g. sat.pot) 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)(.) **/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.pot to your language file, e.g. cd i18n; cp sat.pot 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 |
14 - 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: | 14 - 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: |
15 > msgfmt -o sat.mo fr.po | 15 > msgfmt -o sat.mo fr.po |
16 > mv sat.mo i18n/fr/LC_MESSAGES/sat.mo | 16 > mv sat.mo i18n/fr/LC_MESSAGES/sat.mo |
17 | 17 |
18 - 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: | 18 - 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: |
19 > msgmerge fr.po sat.po > fr2.po | 19 > msgmerge fr.po sat.pot > fr2.po |
20 and if everything is allright | 20 and if everything is allright |
21 > mv fr2.po fr.po | 21 > mv fr2.po fr.po |
22 | 22 |
23 Don't forget that you can (and should !) use the version-control system (mercurial, the "hg" command) to keep history of you translations. | 23 Don't forget that you can (and should !) use the version-control system (mercurial, the "hg" command) to keep history of you translations. |
24 | 24 |