bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Jim Meyering
Subject: Vietnamese .po file causes coreutils build failure [Re: bootstrap: TP urls changed
Date: Thu, 05 Jul 2007 12:03:55 +0200

"Sergey Poznyakoff" <address@hidden> wrote:
> I have installed the following patch:
>
> 2007-07-05  Sergey Poznyakoff  <address@hidden>
>
>         * build-aux/bootstrap (TP_URL,get_translations): Update to use
>         the new TP address.
>         (usage): Fix typo
>         (gnulib_mk): New variable.
...
> -     printf "{ $WGET_COMMAND -O %s/%s.po '\'"$TP_PO_URL"'/%s/%s-%s.%s.po'\'' 
> &&\n", subdir, lang, lang, domain, ver, lang
> -     printf "  msgfmt -c -o /dev/null %s/%s.po || {\n", subdir, lang
> -     printf "    echo >&2 '\'"$0"': omitting translation for %s'\''\n", lang

[ Sorry to Cc so many, but I have two separate requests,
  and it might help if you see the justification. ]

Hi Sergey,

Thanks for updating gnulib's bootstrap script.
However, I see that you've removed the code to detect and exclude
PO files that fail to pass the msgfmt test.  Unfortunately, that is
still needed in order to exclude the erroneous Vietnamese PO file for
coreutils: http://translationproject.org/latest/coreutils/vi.po.

If that PO file is not omitted, coreutils gets a build failure.

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
and permanently, and for all projects that might use this bootstrap script?

Request for the Vietnamese translation team:
============================================

    Would you please fix this file?

        http://translationproject.org/latest/coreutils/vi.po

    Simply removing each line containing: msgstr[1] "" is one way.
    E.g., run this command:

       perl -ni -e '/^msgstr\[1\] ""$/ or print' vi.po

    Otherwise, it causes trouble:
      $ msgfmt -c -o /dev/null vi.po
      vi.po:7: nplurals = 1...
      vi.po:2243: ...but some messages have 2 plural forms
      msgfmt: found 1 fatal error
      [Exit 1]


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?

Thanks,

Jim




reply via email to

[Prev in Thread] Current Thread [Next in Thread]