Mercurial > libervia-backend

comparison README4TRANSLATORS @ 771:bfabeedbf32e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
core: i18n refactoring: - _() is no more installed in __builtin__ - instead, there is a new sat.core.i18n module - added D_() method for deferred translation - languageSwitch method allow to dynamically change translation language - import gettext is tested against ImportError, and dummy methods are used when not available (mainly useful for Libervia)
author Goffi <goffi@goffi.org>
date Sun, 29 Dec 2013 17:06:01 +0100
parents 86d249b6d9b7
children 519e7f79729b
comparison
equal deleted inserted replaced
770:64dd7c0f4feb 771:bfabeedbf32e
1 First of all, thank you for helping translating SàT :) 1 First of all, thank you for helping translating SàT :)
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 - 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): 6
7 > xgettext -L python -d sat sat.tac tools/*py plugins/*py 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:
8 > xgettext -L python -d sat --keyword=D_ -p i18n **/*(.py|.tac|primitivus|wix|jp)(.)
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
8 11
9 - 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
10 13
11 - 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:
12 > msgfmt -o sat.mo fr 15 > msgfmt -o sat.mo fr
17 - 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: 20 - 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 > msgmerge fr.po sat.po > fr2.po 21 > msgmerge fr.po sat.po > fr2.po
19 and if everything is allright 22 and if everything is allright
20 > mv fr2.po fr.po 23 > mv fr2.po fr.po
21 24
22 Don't forget that you can use the version-control system (mercurial, the "hg" command) to keep history of you translations. 25 Don't forget that you can (and should !) use the version-control system (mercurial, the "hg" command) to keep history of you translations.
23 26
24 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. 27 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.
25 28
26 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). 29 Trank you again for you help, don't forget to give me your name and contact email so I can credit you, and don't hesitate to contact me if you need help (goffi@goffi.org, or the sat XMPP room at sat@chat.jabberfr.org).
27 30