| 1 |
|
| 2 |
Thuban Message Translations |
| 3 |
=========================== |
| 4 |
|
| 5 |
Updating the message catalogs currently only works on unix-like systems |
| 6 |
and requires xgettext 0.11. (0.10.x may work for everything but it will |
| 7 |
at least produce a lot of warnings during "make pot" because it doesn't |
| 8 |
know about python syntax.) |
| 9 |
|
| 10 |
- When the thuban sources were edited so that e.g. messages have been |
| 11 |
changed or added, run |
| 12 |
|
| 13 |
$ make pot |
| 14 |
|
| 15 |
to update the thuban.pot file. You also need to do this after a fresh |
| 16 |
CVS checkout to build thuban.pot |
| 17 |
|
| 18 |
- When the thuban.pot file has been changed, run |
| 19 |
|
| 20 |
$ make update-po |
| 21 |
|
| 22 |
to merge the changes in the pot file with the messages already in the |
| 23 |
.po files. |
| 24 |
|
| 25 |
- When the translations in the po files have been changed, run |
| 26 |
|
| 27 |
$ make mo |
| 28 |
|
| 29 |
to generate new .mo files under ../Thuban/Resources/Locale |
| 30 |
|
| 31 |
- The make mo command prints statistics about the translations. To get |
| 32 |
a less verbose version use this: |
| 33 |
|
| 34 |
$ make mo 2>&1 | sed -e 's/ \(messages\|translations\)//g' -e 's/\.$//' |
| 35 |
|
Parent Directory
| 
Revision Log