Difference between revisions of "Translation environment4"

From Gramps
Jump to: navigation, search
m (How it works)
(Files and directory)
Line 34: Line 34:
 
===Files and directory===
 
===Files and directory===
  
Like with [[Translation_environment22#Files_and_directory|previous environment]], we need to list files with translation strings for retrieving messages and generating a 'po/gramps.pot' file.
+
Like with [[Translation_environment22#Files_and_directory|previous environment]], we need to list files with translation strings for retrieving messages and generating a 'po/gramps.pot' file. Process is now only using ''gettext'' and ''python''.
  
* gettext, intltool and 'POTFILES.in' file
+
* gettext, 'POTFILES.in' and 'POTFILES.skip' files
  
 
If you want a script to take your translatable strings into account, you must add your source file path in the file : <code>po/POTFILES.in</code>. For this report example, you should add:
 
If you want a script to take your translatable strings into account, you must add your source file path in the file : <code>po/POTFILES.in</code>. For this report example, you should add:
Line 48: Line 48:
 
  ...
 
  ...
  
See [[Translation_environment22]].
 
 
* xgettext and 'po/gramps' file
 
 
If you want a script to take your translatable strings into account, you must add your source file path in the file : <code>po/gramps</code>. For this report example, you should add:
 
 
...
 
../gramps/plugins/leak.py
 
../gramps/plugins/mediamanager.py
 
../gramps/plugins/myreport.py                # <------
 
../gramps/plugins/narrativeweb.py
 
../gramps/plugins/patchnames.py
 
...
 
  
 
[[Category:Translators/Categories]]
 
[[Category:Translators/Categories]]
 
[[Category:Developers/General]]
 
[[Category:Developers/General]]

Revision as of 02:07, 5 October 2012

This page describes the next translation environment.

See GEPS_026:_Replace_'make'_for_Gramps_build. work in progress (testing stage)

Could be used for Gramps 4.0.x.

How it works

  • intltool (perl), gettext
intltool-update -p

or run:

genpot.sh
  • python, ElementTree[1] and xgettext[2]
python update_po.py -h
python update_po.py --help
  • parser generates a new template and also provides some common features.
    • test flag (-t) will test if 'python' and 'gettext' are properly installed.
  • extract options are everything around extraction for message strings.
    • xml flag (-x) will extract messages from xml based file formats.
    • glade flag (-g) will extract messages from glade file format only.
    • clean flag (-c) will remove created files.
    • pot flag (-p) will create a new catalog.
  • update options are everything around update for translation file(s).
    • merge flag (-m) will merge lang.po file(s) with last catalog.
    • check flag (-k) will check lang.po file(s), will try to compile and will also use check_po script.
  • translation options are some informations about one translation file.
    • untranslate flag (-u) will list untranslated messages.
    • fuzzy flag (-f) will list fuzzy messages.

Files and directory

Like with previous environment, we need to list files with translation strings for retrieving messages and generating a 'po/gramps.pot' file. Process is now only using gettext and python.

  • gettext, 'POTFILES.in' and 'POTFILES.skip' files

If you want a script to take your translatable strings into account, you must add your source file path in the file : po/POTFILES.in. For this report example, you should add:

...
gramps/plugins/leak.py
gramps/plugins/mediamanager.py
gramps/plugins/myreport.py                # <------
gramps/plugins/narrativeweb.py
gramps/plugins/patchnames.py
...