Hi, On Thu, 9 Jul 2015, Axel Braun wrote:
> - Why are the .mo files compiled without error (of course, this > should be the standard case...)?
Does this step use msgfmt?
the command 'compile_catalog' in python setup.py compile_catalog is imported from python-babel - I assume it uses something similar, or even the python implementation of msgfmt. Sorry, I'm just packing, not programming.>> That may be the answer to your first question.
Which one does 'That' refer to? python-babel or not programming`? In fact only some language files are effected by this error message, not all. If the python implementation is inferior then you have the answer.
I have my doubts....I checked the file with poedit and then run msgfmt on it, result:
docb@T520:~/tryton/tryton-3.6.1/b/share/locale/nl_NL/LC_MESSAGES> msgfmt -v -c tryton.po 278 übersetzte Meldungen, 61 ungenaue Übersetzungen, 63 unübersetzte Meldungen.
I use the .mo file generated by msgfmt, but still the error remains: [ 19s] + /usr/lib/rpm/find-lang.sh /home/abuild/rpmbuild/BUILDROOT/tryton-3.6.1-0.i386 tryton --without-C [ 19s] removing translation /usr/share/locale/nl_NL/LC_MESSAGES/tryton.mo: 278 translated messages.
There is no error in the above. The "removing translation" are informative. The error is this from your original log: "<stdin>:81: 'msgid' and 'msgstr' entries do not both end with '\n'" and that means that "msgunfmt $file | msgfmt --statistics -o /dev/null" is breaking, and that means that $file was incorrectly generated when the initial build didn't already complain. So yes, it's the python implementation of msgfmt that's broken. Ciao, Michael.