On 23/08/2012 09:55, F Wolff wrote:
Op Wo, 2012-08-22 om 13:44 -0400 skryf Chris Leonard:
Dear Pootle folks,
I am admittedly running on an older version of Pootle, so please tell
me if this had been identified as an issue and corrected in a newer
version.
Pootle 2.0.5 is powered by Translate Toolkit 1.7.0
Every once and a while, I will commit a PO file from Poolte and get a
complaint back from the developer that the PO file choked and died
during msgmerge in the build process. with an error like this:
Merging cs-CZ.po with abiword.pot...cs-CZ.po.old:9657: duplicate message
definition...
[...]
msgmerge: found 38 fatal errors
When I have looked into these errors, it appears that the duplications
all occur in the obsoleted (#~) strings commented out at the bottom of
the PO file. It therefore looks like it might be happening during
some merge process where strings are commented out if they are no
longer in the current template. However, it does not appear to be a
very common error with the update from templates process, because it
does not happen with all PO files, only a few from time to time. I do
not know if possibly these PO files have been edited and merged with a
tool outside of Pootle and then uploaded with these errors or whether
they are occurring to them while they are resident in Pootle.
Does anyone have any insight into how this might be happening?
Unfortunately these do not show up as errors on any of the pofilter
checks available in Pootle review tab and while it is easily fixed by
deleting the commented-out strings for that PO file and recommitting,
the developers tend to make a big stink about the localizers
submitting PO files that cause fatal errors in the build process. Far
more noise than I think is justified, given how easily this is
corrected, but they really do get worked up about it. It is a
recurring source of tension between localizers and developers and I
would like to address it, but I do not have the time to do a download
and msgfmt check on every PO file before the commit button is clicked
in Pootle. Besides, commit is typically done by language
administrators and getting all of them do take such a step is not
going to be successful. It does cause developers to distrust Pootle,
so I think it is worth some investigation.
I suppose a pofilter duplicate check that does not ignore the
obsoleted strings could detect this (assuming that the current check
does ignore thsoe strings). I am also curious about the possible
source of this error type and would appreciate any insights you can
provide.
To my best knowledge this has long been fixed, probably at the time of
Pootle version 2.1.0.
If I recall the issue if obsolete strings that get resurrected i.e. go
from Obsolete back to Translatable. And yes this was fixed in a newer
Pootle. You could try going through changes to work out which version
but my guess is you might want to upgrade instead.
--
Dwayne Bailey
+27 12 460 1095
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle
