Mercurial > libervia-backend
annotate README4TRANSLATORS @ 853:c2f6ada7858f
core (sqlite): automatic database update:
- new Updater class check database consistency (by calculating a hash on the .schema), and updates base if necessary
- database now has a version (1 for current, 0 will be for 0.3's database), for each change this version will be increased
- creation statements and update statements are in the form of dict of dict with tuples. There is a help text at the top of the module to explain how it works
- if we are on a development version, the updater try to update the database automaticaly (without deleting table or columns). The Updater.generateUpdateData method can be used to ease the creation of update data (i.e. the dictionary at the top, see the one for the key 1 for an example).
- if there is an inconsistency, an exception is raised, and a message indicate the SQL statements that should fix the situation.
- well... this is rather complicated, a KISS method would maybe have been better. The future will say if we need to simplify it :-/
- new DatabaseError exception
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Sun, 23 Feb 2014 23:30:32 +0100 |
| parents | 519e7f79729b |
| children | ca7a2bf4fb40 |
| 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 |
| 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: | |
|
845
519e7f79729b
misc: exclude misc/_jp from xgettext input
souliane <souliane@mailoo.org>
parents:
771
diff
changeset
|
8 > xgettext -L python -d sat --keyword=D_ -p i18n **/*(.py|.tac|primitivus|wix)(.) **/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: | |
| 15 > msgfmt -o sat.mo fr | |
| 16 > mv sat.mo i18n/fr/LC_MESSAGES/sat.mo | |
| 17 | |
| 18 /!\ Note that you don't need to precise the file extention mith the msgfmt command, here fr mean "use fr.po file" | |
| 19 | |
| 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: | |
| 21 > msgmerge fr.po sat.po > fr2.po | |
| 22 and if everything is allright | |
| 23 > mv fr2.po fr.po | |
| 24 | |
| 771 | 25 Don't forget that you can (and should !) use the version-control system (mercurial, the "hg" command) to keep history of you translations. |
| 69 | 26 |
| 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. | |
| 28 | |
| 771 | 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). |
| 69 | 30 |