On Mon, Feb 23, 2009 at 02:51:20PM -0600, Hyrum K. Wright wrote:
> On Feb 23, 2009, at 2:32 PM, Jens Seidel wrote:
>> On Mon, Feb 23, 2009 at 11:28:31AM -0600, Hyrum K. Wright wrote:
>> Yep, please subscribe me!
>>
>>>>> I don't know if they are specifically related to this commit or
>>>>> not,
Yep, it is.
>>>>> but I currently get the following error when running 'make':
>>>>>
>>>>> /opt/local/bin/msgfmt -c -o subversion/po/de.mo subversion/po/de.po
>>>>> subversion/po/de.po:456:1: syntax error
>>
>> It works with version 0.15 which is quite old.
>
> dhcp-198-227:svn-trunk Hyrum$ gettext --version
> gettext (GNU gettext-runtime) 0.17
Right, I could reproduce it with this version. I think this is a bug
in gettext and will write a bugreport. The order of comments in PO files
should not matter but version 0.15 reordered the comments wrong when working
on files created with version 0.17.
I fixed it in
r36085 | jensseidel | 2009-02-23 22:27:30 +0100 (Mo, 23. Feb 2009) | 4 lines
* subversion/po/de.po: Reorder gettext comments so that #| is the last one.
Otherwise gettext v. 0.17 reports (bogusly??) syntax errors. Current order
results from partly using the older version 0.15.
>> I suggest you analyse the problem, I really doubt that even older
>> gettext
>> versions have trouble with the current PO file.
>
> I have no idea *how* to analyze the problem. Nothing on my side has
> changed. When I update to r36000 of the file, the problem disappears.
> Such changes behavior should be considered a bug.
Yep, but it is not necessarily a bug introduced in the commit but could also
a bug in the toolchain which gets visible with r36000 :-)
I have a checkout of Subversion which I made in the past with a trunk
snapshot of Subversion. This working copy format cannot be parsed with
a stable version of Subversion so I have to work on the PC where the
snapshot of Subversion (and an very old gettext) is installed ...
> Is there a compelling reason to use whatever feature is causing this
> breakage?
Of course otherwise I wouldn't do it :-)
Quoting http://www.gnu.org/software/gettext/manual/gettext.html:
"The previous-untranslated-string is optionally inserted by the msgmerge
program, at the same time when it marks a message fuzzy. It helps the
translator to see which changes were done by the developers on the
untranslated-string."
There exist also some graphical PO editors (which I do not yet use) which
are able to visualize the changes in a message which made a message fuzzy.
See http://www.mail-archive.com/debian-i18n%40lists.debian.org/msg12349.html
and further mails on the list debian-i18n from recent days for a link to
such programs, advantages, ...
> It is only happening with de.po, which indicates that other
> translators are working reasonably well without it.
Probably because they just do not know about it. I also mentioned already
that it's not yet activated by default for backward compatibility reasons.
Jens
Received on 2009-02-23 23:06:08 CET