Parent Directory
|
Revision Log
* Thuban/__init__.py (_): Implement the translation function for real using the python gettext module. * Thuban/UI/classifier.py (ClassTable.GetRowLabelValue): Don't translate empty strings. * Thuban/UI/application.py (ThubanApplication.read_startup_files): Add a missing space to a warning message * po/README: New. Notes about the management of the translation files. * po/Makefile: New. Makefile to help manage the translation files. * po/es.po: New. Spanish translation by Daniel Calvelo Aros * MANIFEST.in: Include the *.mo files in Resources/Locale and the translations and support files in po/ * setup.py (data_files): Add the *.mo files to the data_files too * README: Add note about the translations when building from CVS
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 |
Name | Value |
---|---|
svn:eol-style | native |
svn:keywords | Author Date Id Revision |
[email protected] | ViewVC Help |
Powered by ViewVC 1.1.26 |