I commited changes on rev16351:
* trunk/po/POTFILES.in missed src/plugins/lib/libtreebase.py
* new template (gramps.pot) because there was new strings and fixed typos; do not need to use old references
* fr.po; just to see if merging is still available and nothing lost
> you went about fixing the errors or pointing to a source of help
For es.po, tr.po, pt_PT.po, 'svn diff' or patch revision will not help (too many changes). In theory, diff should be done without context (file reference). Even without them, they are big textual files, so line number should be also ignored!
One way will be to format them (msgfmt) then unformat them (msgunfmt) before and after the change, then to make a diff!
Anyway, we have line references (could be open into a text editor with UTF-8 support):
tr.po:1816: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The string ends in the
middle of a directive.
1815 msgid "%(father)s and %(mother)s"
1816 msgstr "%(baba)s ve %(anne)"
1. Should be marked as fuzzy (need review)
2. Should keep %(father)s, %(mother)s
3. one string mark is missing: %(anne)
The fatal error was the 3.
tr.po:20237: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The string ends in the
middle of a directive.
20236 msgid "%(date)s in %(place)s"
20237 msgstr "%(Tarih)inin %(yeri)"
Same errors as before (see above)
Typo might generate "fatal" errors, which means we can generate error into Gramps! When code uses "%(father)s and %(mother)s", the translation returns "%(baba)s ve %(anne)", this will generate errors. To mark this type of string as fuzzy is our first security, in this case this returns "%(father)s and %(mother)s", like an untranslated string.
--- En date de : Dim 9.1.11, Dale Athanasias <dalegrind@...> a écrit :
De: Dale Athanasias <dalegrind@...>
Objet: RE: [Gramps-devel] Translations in trunk failed the correctness check run on gettext (es.po / pt_PT.po / tr.po )
Date: Dimanche 9 janvier 2011, 0h05
Thank you for fixing them.
Would you mind sharing how you went about fixing the errors or pointing to a source of help?
> Date: Sat, 8 Jan 2011 10:59:39 +0100
> From: romjerome@...
> To: dalegrind@...
> CC: gramps-devel@...
> Subject: Re: [Gramps-devel] Translations in trunk failed the correctness check run on gettext (es.po / pt_PT.po / tr.po )
> Thank you, this should be fixed on rev16351:
> Note, there is some strange (Chinese ?) letters on tr.po
> They are not used (fuzzy) but they are present since many versions.
> I guess it was a wrong commit. Anyway, Turkish support is disable on
> installation (release). Like Serbian, Romanian, Macedonian, Esperanto,
> Breton, Arabic; they all wait for new translators.
> It was plural forms errors on pt_PT.po
> One string/argument problem on es.po.
> Happy new year too!