Translation environment4

From Gramps
Revision as of 09:08, 5 October 2012 by Romjerome (talk | contribs) (How it works)
Jump to: navigation, search

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:
  • python, ElementTree[1] and xgettext[2]
python -h
python --help

For generating a new template:

python -p
  • 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, '' 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/ For this report example, you should add:

gramps/plugins/                # <------