Changes

{{languages|Translating Gramps}} Tips for translators of the GRAMPS Gramps program. The page [[Category:Translators/CategoriesCoding_for_translation|coding for translation]]may also be of interest to translators. Please read [[Category:Developers/GeneralA Translators Guide to Git]]

# : gramps.py:10

* text after ''# '' provides a comment, the .** The file reference and the line numberafter ''#:'' ** A comment on code or the main string (''msgid'') after ''#. ''** A comment on your translation (''msgstr'') after ''#''This will help translator but is optional for having a translation.* ''#, fuzzy'' could be added because string is not up-to-date. It means that there was a change somewhere (a string has been added, removed or modified) and ''xgettext'' did a guess on what the translation should be. This guess is most likely not entirely correct, but it is often very close.''fuzzy'' strings are ignored, english string (''msgid'') will be used ! Need to correct/validate entry on your translation editor.

* msgstr is your translation ''fuzzy'' could be added because string is not up-to-date. It means that there was a change somewhere (a string has been added, removed or modified) and ''xgettext'' did a guess on what the translation should be. This guess is most likely not entirely correct, but it is often very close.

# Always save your translations in UTF-8 encoding'''without [https://en.wikipedia.org/wiki/Byte-order_mark BOM]''' ([http://achilles-keep-moving.blogspot.de/2011/10/msgfmt-fatal-error-with-utf-8-with-bom.html take care with ''NotePad''])

Translating GRAMPS Gramps into a new language means translating English strings used in the GRAMPS Gramps interface. To put it shortly, this amounts to

# getting the translated file uploaded into gramps SVN the Gramps Git repository.Another avenue of translation is translating the documentation. This is a different and lengthy process and it is decribed described in our [[Translating the Gramps User manual]] page. Here we will concentrate on the interface translation only.

* Download <code>gramps.pot</code> from GRAMPS SVN Gramps Git repository, see [[Brief_introduction_to_SVNBrief_introduction_to_Git| the introduction to SVNGit]].You can also download files by browsing via [https://github.com/gramps-project/gramps GitHub web interface].* Look for <code>gramps.pot</code> in the directory <code>gramps30/'''po</code> or if you looking for the trunk version look for <code>gramps.pot</code> in the ''' directory <code>trunk/po</code>.

* Use [http://gtranslator.sourceforge.net GTtranslator] (GNOME, windows), [http://kbabeli18n.kde.org/tools/ KBabel] (KDE), [http://userbase.kde.org/Lokalize Lokalize] (KDE, windows), Emacs po-mode, [http://translatevirtaal.sourceforgetranslatehouse.net/wiki/pootling/index pootlingorg Virtaal] (GNU/Linux, Mac, windows), [http://www.poedit.net/ poedit] (GNU/Linux, OSX, windows), or any similar tool designed for translating <code>.po</code> files. If you do not like any of these tools, you can use any text editor to translate messages. If using vim, properly setting the "langmap" option will significantly speed up your work.* Even though GRAMPS Gramps uses UNICODE (UTF-8) for its character set, you may use your native character set for your translation. Just make sure you specify the character set you are using in the <code>Content-Type</code> line in the <code>.po</code> file. GRAMPS Gramps will handle the conversion to UNICODE.* If there are non ASCII characters in the original English string, try to preserve them by copying them, if applicable.

As an extension to standard gettext, strings in GRAMPS Gramps can have a context prefix. This prefix should '''not''' be translated, and just be deleted in the translation. More info and an example [[#Translation context|further down]].

As a special context, you will see the manual context, eg <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, :

these strings should only be translated if a '''wiki user manual ''' is available in your language, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e. g.</abbr>, in Dutch : 'Datums_aanpassen'  The string refers to a section, eg <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, [[Gramps_3Gramps_4.0_Wiki_Manual_1_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_Detailed_-_part_1#Editing_Dates Editing_dates |Editing_Dates]] in Dutch becomes [[Gramps_3Gramps_4.0_Wiki_Manual_1_Wiki_Manual_-_Entering_and_Editing_Data:_Detailed_Detailed_-_part_1/nlde#Datums_aanpassenDaten_bearbeiten|Datums_aanpassen]].

# In the directory <code>gramps30/po</code> or the <code>trunk/po</code> directory run the command: <pre>make</pre> If there are errors in your po file, this will fail and give you an error message. You should correct these errors. If you have trouble understanding the error, try to run the next test, which might give a more verbose output.# In the directory <code>gramps30/po</code> or the <code>trunk/po</code> run the command: <pre> ./check_po --skip-fuzzy lang.po</pre> or <pre> python check_po --skip-fuzzy lang.po</pre> or <pre>alternative under Windows OS ???</pre>, langwhere lang is your language code. This will give you errors in your translation, information on badly translated phrases, ... the output could resemble something like this..

You can see that there are 3816 strings to be translated and the coverage is around 96 %. There are still 12 untranslated strings and some 120 fuzzies. The last one can be ok, but should be checked. Additional information shows <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g. </abbr>, that in 15 strings there is a mismatch with the 'last character':

# ====statistics==== In the directory <code>gramps30/po</code> or directory run the command: <codepre>trunk/msgfmt --statistics lang.po</codepre> run the command: or <pre>msgfmt .exe --statistics lang.po</pre> where lang is your language code. This should not throw an error.* Basically this gives the same info in a condensed format: 3533 translated messages, 125 fuzzy translations, 12 untranslated messages.

For checking syntax (header, format, domain) :

* Currently, [[Coding_for_translation#How_it_works|formatting (msgfmt) is performed during build time]], so you should not have to worry about it. The translated <code>.po</code> file is the product of your work. However, try to [[Translating_Gramps#Save_as_.mo_file|check syntax]] before any commit. ===Send your contribution=== Check it into SVN Git if you obtained the permission to do so, or email it . The following configuration option simplifies pushing a branch back to [[Contact|Brian or Benny]] otherwisethe server: $ git config --global push.default upstream Otherwise you can fork gramps repository with a Github account and pull a merge request. See: {{Code Browser}}

If you have submitted a translation, changes are it may well be that after some weeks/months, new strings are added to GRAMPSGramps, implying you need to update your translation file.

Assuming you have obtained originally the GRAMPS Gramps source tree as explained in [[Brief introduction to SVNGit]]. Now:* Update your gramps Gramps tree from SVNGit. This can be done by executing the command <pre>svn upgit pull --rebase</pre> from the root GRAMPS svn Gramps directory. This will download an updated <code>gramps.pot</code> file.* Use your outdated translation to translate the strings that did not change:<pre>msgmerge lang.po gramps.pot -o newlang.po</pre> or <pre>msgmerge --no-wrap lang.po gramps.pot -o newlang.po</pre> where <code>lang</code> is your language code. The <code>--no-wrap</code> option will prevent changes due to automatic word wrapping, use it if your previous po file was constructed like that. The <code>--no-wrap</code> options allows for more readable SVN Git diffs.* Translate Check fuzzy messages and translate all untranslated messages in <code>newlang.po</code>. When you are sure everything is right, rename <code>newlang.po</code> as <code>lang.po</code> and check it into SVN Git as you did with the original file.* If command <code>msgmerge</code> is not available on your system, you have to install the <code>}gettext</code> package. For [http://wiki.wxpython.org/index.cgi/Internationalization#head-d8e0d98b64f3878f8bb828aeb41a05bcc6a02cc4 How_to_get_gettext_tools_for_Win32 windows users].* To back-port translations, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, to merge master branch translations onto an earlier branch, do this on the earlier branch (assuming gramps.pot is updated):<pre>msgmerge -C lang.po master-lang.po gramps.pot -o newlang.po</pre>. Then resolve the fuzzies as usual.

make gramps.pot/genpot.sh or python update_po.py -p see [[Talk:Translation_environment4|differences between tools]].

make updatecd po python update_po -pom all in the <code>po</code> directory. This assumes that you have already succesfully successfully configured the source.Note, this command ignores <code>--no-wrap</code> option, so not practical for Git diffs. {{man warn|Environment change|For Gramps 4.0, {{stable_branch}} and master, see [[Translation_environment4|new environment]].}}

<pre> python check_po --skip-fuzzy newlang.po</pre>. If everything is ok, the output will be something like this:

This should install your translations to <code>''/usr/share/locale/xx{lang}/LC_MESSAGES/gramps.mo</code>'', with xx {lang} being your language. You could of course copy your files manually to that dir with the gramps.mo name. Make sure you only install from within the po directory, or you will install the development version of Gramps, which is not supported and for testing only! ==== Running the master branch with your translation ====

Make sure you only install from within The i18n data are often under ''../share/locale'' according to the po directory, or you will install the development version of GRAMPS, which is not supported and for testing only!default prefix.

The current GRAMPS trunk python setup.py build python setup.py install #as of February 2009 by default looks for the i18n data under <code>/usr/local/share/locale</code>. So you can use:root !

This will install the .mo files under ''../autogenshare/locale/xx/LC_MESSAGES'', according to the default prefix set.sh or make cd popython setup.py build make python setup.py install --root=/home/joe/gramps --prefix="/home/joe/gramps4" --enable-packager-mode #as simple user ! This will install Gramps and translations under your ''/home/...'' directory. ===== $GRAMPSI18N (for your locale) ===== Actually you don't even need to install the files in order to test them. This is useful because you can develop Gramps without needing superuser privileges. Bear in mind the Gramps i18n process goes something like this when you use the master branch: * when you type <code>python build</code> in the source tree root !(/home/user/Gramps <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>) all the po/*.po files are compiled into build/mo/{lang}/*.mo files.* when you type <code>python install</code> inside the po directory, these .mo files are copied to {prefix}/share/locale/{lang}/LC_MESSAGES as gramps.mo files.

This will install But you can change the place where Gramps looks for these files by altering the environment variable $GRAMPSI18N.mo files under So you could also for instance do something like this and avoid the <code>python setup install</usr/local/share/locale/xx/LC_MESSAGES, since code> step: (if you are using csh or tcsh the default prefix is /usr/localsyntax would be a little different)

===== [user@localhost /home/user/Gramps]$ mkdir -p po/en_GB/LC_MESSAGES [user@localhost /home/user/Gramps]$ cp po/en_GB.gmo po/en_GB/LC_MESSAGES/gramps.mo [user@localhost /home/user/Gramps]$ cd gramps [user@localhost /home/user/Gramps/src]$GRAMPSI18N =$PWD/../po LANG====en_GB.UTF-8 python gramps.py

Actually you don't even need to install the files in order to test them===== gramps. This is useful because you can develop GRAMPS without needing superuser privileges. Bear in mind the GRAMPS i18n proccess goes something like this when you use trunk:sh =====

* when you type On a gramps launcher (copy from ''<code>make{prefix}/bin/gramps</code> in the source tree root (/home/user/trunk e.g.'') all the trunkyou can set : export GRAMPSDIR=/po/*.po files are compiled into trunk/po/*.gmo files.* when you type <code>make install< export GRAMPSI18N=/code> inside the /home/user/trunk/po directory, these .gmo files are copied to /usr/local/share/locale/xx/LC_MESSAGES as gramps.mo files.

But you can change the place where GRAMPS looks for these files by altering Where the environment variable ''$GRAMPSI18NGRAMPSDIR'' is the path to your ''gramps'' directory. So you could also for intance do something like this and avoid the <code>make install</code> step: (if you are using csh or tcsh the syntax would be a little different)

[user@localhost /home/user/trunk]$ mkdir -p po/en_GB/LC_MESSAGES [user@localhost /home/user/trunk]$ cp po/en_GB.gmo po/en_GB/LC_MESSAGES/gramps.mo [user@localhost /home/user/trunk]$ cd src [user@localhost /home/user/trunk/src]Where the environment variable ''$ GRAMPSI18N=$PWD/../po LANG=en_GB.UTF-8 python '' is the path to your ''grampslocale'' directory.py

If you don't want to compile all translations, you may save your ''.po'' file as ''.mo'' file, or use ''msgfmt'' utility on /po directory:  msgfmt -o gramps.mo your_lang.po

msgfmt .exe -o gramps.mo your_lang.po

this will create a messages''gramps.mo '' file, a compiled version of your ''.po'' file.Rename messages.mo to gramps.mo and put Put it on your translation path (''see above'').

==Hard to Translate Phrasestranslate phrases==

===Gramps terminology===There are terms with special significance in computer software. The terms are often creatively awkward constructs in English... just so the term is more unique and stands out in a sentence. Translating the words literally or substituting a translation of the underlying concept may not be workable. It may be necessary to become ''creative'' and substitute a similarly awkward (and short!) label in your target language. The labels of some Gramps core concepts or interface elements hold that higher level of significance. These must be translated consistently between the User Interface and the Wiki. (Inconsistent translations will confuse the users.)  ''Example:'' The '''[[Gramps_Glossary#active_person|Active Person]]''' in Gramps is not a person with a healthy amount of vigorous physical exercise. Instead, it is the record from the [[Gramps_Glossary#people|People]] [[Gramps_Glossary#category|Category]] that is the focal center of reference for display &amp; change. Neither would translate into a memorable label. The [[Gramps Glossary]] is a good resource for understanding the context and significance of such terms. If you translate the Glossary and then alphabetize the translated terms, also leave an ID SPAN with the untranslated English term. This allows hotlinks from untranslated pages to work in unison with translated hotlinks.  If it becomes necessary to be ''creative'' translating a term, please add a [[Translating_Gramps#Language_specific_pages|language specific]] reference page for your language. This helps other Translators share your style of creativity. ===LDS Terminologyterminology===

First, translators need to check if information is available on .po header:''"Plural-Forms:\n"''. (See [http://translate.sourceforge.net/wiki/l10n/pluralforms samples])

msgstr_plural msgid_plural "%d seconds"

msgstr_plural msgid_plural "%d hours"

msgstr_plural msgid_plural "%d seconds"

===Translating mnemonicskeys(Keyboard Shortcut keys)===Mnemonics are accelerator keys (also known as Keyboard Shortcut keys) you find in labels, accessible by pressing the {{man key press|ALT }} key together with the mnemonic. You see then in the translated text with a low line, eg <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, '_Help' is shown as 'Help' with a line an underline under the H, and can be put to focus/selected by pressing {{man key press|ALT+|h}}.

*"If duplication of access keys in a window is unavoidable, you should still refrain from duplicating the access keys for any of these buttons that appear in the same window: {{man button|OK}}, {{man button|Cancel}}, {{man button|Close}}, {{man button|Apply }} or {{man button|Help}}."

'''{{man warn|Warning''': some |Some fonts family will not properly display mnemonics on "g", "j", "p", "q" or "y" as these print the letter over the line under it making it very hard to distinguish the small line. Please avoid to use mnemonics key bindings on these letters. Also try to avoid i and l, as people have difficulty distinguishing between those.}}

Capital letters are no problem though, underlining eg <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, G will work just fine as the letter does not write over the line.

In short, the need for a plugin comes from the impossibility to translate "first cousin twice removed" in languages such as, <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, German or Russian. See the [[Relationship Calculator]] page for details on why and how to create such a plugin.

For the development version (trunkmaster branch) version you can find the required starting files under the directory (/trunk)/data/man. You will find the files

<code>cd data/man</code> and do  <code> mkdir xx</code> where xx is your languagecode (fr for French, sv for Swedish, etc.) You should use Git. See [[Brief_introduction_to_Git| the introduction to Git]].

Because you added new files, SVN requires that you set All changes must be committed and pushed to the correct propset for those files. Two things are to be done.<code>server: svn propset svn:mime git commit -type text/plain xx/gramps.1.in xx/Makefile.am svn propset svn:eol-type native xx/gramps.1.in "Add man page for xx/Makefile.am"</code> git push

You could also in should see no errors when you run the config file of subversion ( HOMEDIR/.subversion/config) enable the auto-prop feature (enable-auto-props = yes) and uncomment the relevant lines in the [auto-props] section.All changes must be committed and do not forget to change the ChangeLog file.

You should see no errors when you run the <code> ./configure</code><br/> <code>make</code> <br/>scripts.

<code>sudo make install</code> This will put the gramps.1.gz file into /usr/local/share/man/xx/man1 directory. You could also use a prefix. Then you do: <code>sudo make --prefix=/usr/share install</code> To see the result of your work, do: <code> man -L xx gramps</code>

To have enable the weblink for help when pressing the link working {{man button|F1}} button in GRAMPSthe Gramps program, you need to have or edit the GrampsDisplay.py file <code>MANUALS</code> variable to contain your language.On line 30 of that file, you seecode locale in the:

This maps These entries map a language code to the extension used on the wiki, so to add french, change this too:

*Every '<code>manual|...</code>' entry in the <code>gramp.pot </code> file refers to a section in the manual, so make sure to use good section headings so this does not change too much over time.Note that reports/tools link to a section in the page with the same name as the report name in GRAMPSGramps. *You should be able to edit directly on wiki or using tools like [http://translate.sourceforge.net/wiki/toolkit/txt2po txt2po] or [http://po4a.alioth.debian.org/ po4a]. Also previous gettext file for the manual and [http://en.wikipedia.org/wiki/Translation_memory Translation Memory] may help you to upgrade deprecated/old gettext files. <abbr title="exempli gratia - Latin phrase meaning 'for example'">e.g.</abbr>, store existing entries from ''/usr/share/locale''. ==Language specific pages==Check out the pages which cover some aspects of translation into a specific language, such as the glossary. *[[Translation into Finnish|Finnish]]*[[Translation into French|French (Français)]]*[[Translation into Russian|Russian]]

==Translating third-party plugins==As * See [[Addons_development#Get_translators_to_translate_your_addon_into_multiple_languages|Third-party Pluginsaddons for Gramps]] are not officially part of GRAMPS and are not supported by the GRAMPS Developers but give users more tools to work with your genealogy data in GRAMPS, we can translate them !.

Trying to avoid duplicate strings which could generate conflicts, [[MediaCategory:additional.pot.gz|here an additional templateTranslators/Categories]]. We should be able to copy[[Category:Developers/paste references at the end of main translation file for supporting translation on third-party plugins.General]]