Re: Vietnamese .po file causes coreutils build failure [Re: bootstrap: TP urls changed

[Jim Meyering]

Benno Schulenberg <address@hidden> wrote:
> Jim Meyering wrote:
>> You can argue that the translation project should not publish
>> such a .po file, and I agree that "upstream" (in the TP
>> .po-checking code) is the right place to fix this, but can you
>> get them to fix it quickly
>
> I've run the following on all files in the latest/ directory that
> had the same problem, among them coreutils/ja.po:
>
>     sed -i '/msgstr\[1\]/d' the.po
>
> And checked that they now pass 'msgfmt -c -o /dev/null the.po'.

Thanks for the quick work!

> (There's still one coreutils po file for which 'msgfmt -c' reports a
> fatal error, but I can't see anything wrong with the indicated
> messages.  It might be a bug in 'msgfmt'.
>
> coreutils/be.po:2298: number of format specifications in 'msgid' and
> 'msgstr[0]' does not match
> coreutils/be.po:2306: number of format specifications in 'msgid' and
> 'msgstr[0]' does not match
> msgfmt: found 2 fatal errors)

That's odd.
I have no problem here.  But my be.po file has
already been merged, so it's no longer the same as yours.

>> Request for the TP coordinator:
>> ===============================
>>
>>     Would you please consider adding a msgfmt check like the one
>> above, to prevent publication of any new .po file with that
>> error?
>
> I've just now tried uploading a grep-2.5.1a.nl.po file containing
> the "...but some messages have 2 plural forms" error -- it gets
> rejected.  So the check is apparently already in place.

Great.  Thanks for checking.