Changeset 239
- Timestamp:
- 07/13/07 17:31:11 (5 years ago)
- File:
-
- 1 edited
-
trunk/README (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/README
r238 r239 11 11 4. DOCUMENTATION 12 12 5. HACKING 13 6. TRANSLATI NG13 6. TRANSLATIONS 14 14 7. RELEASE NOTES 15 15 8. PROGRAM CREDITS … … 64 64 If you intend to change Itaka source code, please read the HACKING file. 65 65 66 6. TRANSLATI NG:66 6. TRANSLATIONS: 67 67 68 68 Translating Itaka to another language is quite easy, you first need GNU gettext installed. … … 70 70 Each stable Itaka version will ship with a .pot template file located in 71 71 locale/itaka.pot. This template includes all the up to date code strings, and 72 i s the base you should use to create your translation.72 it's the base you should use to create your translation. 73 73 74 If you've changed any strings, the itaka.pot file can be regenerated by doing: 75 $ xgettext -o locale/itaka.pot *.py 74 If you've changed any stringsin in the code, the itaka.pot file can be regenerated by doing: 75 $ xgettext -oj locale/itaka.pot *.py 76 # If you find duplicates, do: 76 77 $ msguniq -o locale/itaka.pot locale/itaka.pot 77 78 … … 93 94 94 95 If you want to update existings translations, follow the steps to regenerate 95 the .pot template if code was changed, then do the following :96 the .pot template if code was changed, then do the following to merge the new changes with your translation file: 96 97 97 $ msgmerge -U l anguage.poitaka.pot98 $ msgmerge -U locale/lang/LC_MESSAGES/language.po locale/itaka.pot 98 99 99 100 For more information, please see the GNU gettext manual at http://www.gnu.org/software/gettext/manual/gettext.html
Note: See TracChangeset
for help on using the changeset viewer.

