Mercurial > libervia-backend
annotate README4TRANSLATORS @ 2807:0b7ce5daee9b
plugin XEP-0277: blog items data are now entirely serialised before going to bridge:
So far, and for historical reasons, blog items data where serialised using a unicode: unicode dict, which was causing trouble for many types of values (timestamps, booleans, lists).
This patch changes it by serialising the whole items before going to bridge, and deserialising it when going back. This way, complex data can be used easily in items.
This impact psEvent and serItemsData* methods which are renamed transItemsData* because there are not always serialising anymore (a new argument "serialise" allows to specify it).
When editing a blog post in jp, metadata are now more easy to manipulate, specially lists like tags.
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sat, 23 Feb 2019 18:59:00 +0100 |
| parents | 0db0013c59dd |
| children | 5e72efd2f95d |
| rev | line source |
|---|---|
| 69 | 1 First of all, thank you for helping translating SàT :) |
| 2 | |
| 223 | 3 NOTE: *.po files are in i18n directory |
| 4 | |
| 69 | 5 To translate a file, you can use a dedicated tool as the excellent gtranslator: |
| 771 | 6 |
|
862
ca7a2bf4fb40
i18n: updated the translation files
souliane <souliane@mailoo.org>
parents:
845
diff
changeset
|
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: |
|
1291
0db0013c59dd
remove remaining references to Wix
souliane <souliane@mailoo.org>
parents:
862
diff
changeset
|
8 > xgettext -L python -d sat --keyword=D_ -p i18n **/*(.py|.tac|primitivus)(.) **/jp(.) |
| 771 | 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 | |
| 69 | 11 |
| 12 - use the choosed tool (a simple text editor can be sufficient) to edit the file: e.g. gtranslator fr.po | |
| 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: | |
|
862
ca7a2bf4fb40
i18n: updated the translation files
souliane <souliane@mailoo.org>
parents:
845
diff
changeset
|
15 > msgfmt -o sat.mo fr.po |
| 69 | 16 > mv sat.mo i18n/fr/LC_MESSAGES/sat.mo |
| 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: | |
| 19 > msgmerge fr.po sat.po > fr2.po | |
| 20 and if everything is allright | |
| 21 > mv fr2.po fr.po | |
| 22 | |
| 771 | 23 Don't forget that you can (and should !) use the version-control system (mercurial, the "hg" command) to keep history of you translations. |
| 69 | 24 |
| 25 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. | |
| 26 | |
|
862
ca7a2bf4fb40
i18n: updated the translation files
souliane <souliane@mailoo.org>
parents:
845
diff
changeset
|
27 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). |
| 69 | 28 |