Mercurial > libervia-backend
view README4TRANSLATORS @ 1033:d87aa6bdb0b4
jp: option '-c' is not longer a flag but a string to define the profile password:
- no '-c': same behavior as before, do not connect the profile
- '-c' with not following value: autoconnect and use the default value '' as profile password
- '-c' with a following value: autoconnect and use that value as profile password
Note that previous scripts may not work. For example, even if the profile password for "test1" is empty:
jp disco -p test1 -c contact@host.net
must be changed to:
jp disco -p test1 -c -- contact@host.net
Otherwise, argparse will think that "contact@host.net" is the password and that the target JID is missing.
author | souliane <souliane@mailoo.org> |
---|---|
date | Wed, 07 May 2014 16:10:20 +0200 |
parents | ca7a2bf4fb40 |
children | 0db0013c59dd |
line wrap: on
line source
First of all, thank you for helping translating SàT :) NOTE: *.po files are in i18n directory 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, the following command use zsh's globbing syntax), launched from root sat dir after having emptied the build directory: > xgettext -L python -d sat --keyword=D_ -p i18n **/*(.py|.tac|primitivus|wix)(.) **/jp(.) - then to start a new translation, copy i18n/sat.po to your language file, e.g. cd i18n; cp sat.po fr.po - 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.po > mv sat.mo i18n/fr/LC_MESSAGES/sat.mo - 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 (and should !) 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. Thank 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).