Changes

Jump to: navigation, search

Translation environment22

760 bytes added, 12:39, 3 October 2012
no edit summary
From Gramps '''2.2.x''' to Gramps '''{{stable_branch}}'''.
 
==How it works==
[http://www.gnu.org/software/gettext/manual/gettext.html GNU gettext] and [http://live.gnome.org/TranslationProject/DevGuidelines/Localize%20using%20gettext%20and%20intltool Gnome] provide utilities and a [http://www.gnome.org/~malcolm/i18n/build-changes.html translation framework]:
# Merges translated strings into key file, ''root'' directory :
intltool-merge -k po/ data/gramps.keys.in data/gramps.keys
 
===Files and directory===
 
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:
 
...
# plugins directory
src/plugins/AncestorChart2.py
src/plugins/AncestorReport.py
...
src/plugins/FindDupes.py
src/plugins/Leak.py
src/plugins/MediaManager.py
src/plugins/Myreport.py # <------
src/plugins/NarrativeWeb.py
src/plugins/PatchNames.py
...
 
In this file, the sources are sorted within each directory or category.
 
You can check missing references (not on <code>POTFILES.in</code> and <code>POTFILES.skip</code>) with the command
/intltool-update -m
into <code>/po</code> directory.
 
[[Category:Translators/Categories]]
[[Category:Developers/General]]

Navigation menu