Changeset 239 for trunk


Ignore:
Timestamp:
07/13/07 17:31:11 (5 years ago)
Author:
marc
Message:

README updates

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/README

    r238 r239  
    11114. DOCUMENTATION 
    12125. HACKING 
    13 6. TRANSLATING 
     136. TRANSLATIONS 
    14147. RELEASE NOTES 
    15158. PROGRAM CREDITS 
     
    6464If you intend to change Itaka source code, please read the HACKING file. 
    6565 
    66 6. TRANSLATING: 
     666. TRANSLATIONS: 
    6767 
    6868Translating Itaka to another language is quite easy, you first need GNU gettext installed.  
     
    7070Each stable Itaka version will ship with a .pot template file located in 
    7171locale/itaka.pot. This template includes all the up to date code strings, and 
    72 is the base you should use to create your translation. 
     72it's the base you should use to create your translation. 
    7373 
    74 If you've changed any strings, the itaka.pot file can be regenerated by doing: 
    75     $ xgettext -o locale/itaka.pot *.py 
     74If 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: 
    7677    $ msguniq -o locale/itaka.pot locale/itaka.pot 
    7778 
     
    9394 
    9495If you want to update existings translations, follow the steps to regenerate 
    95 the .pot template if code was changed, then do the following: 
     96the .pot template if code was changed, then do the following to merge the new changes with your translation file: 
    9697 
    97     $ msgmerge -U language.po itaka.pot 
     98    $ msgmerge -U locale/lang/LC_MESSAGES/language.po locale/itaka.pot 
    9899 
    99100For 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.