This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] gettext support for GCC 4.0 internal format, fix for PRtranslation/21364
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Bruno Haible <bruno at clisp dot org>, gcc-patches at gcc dot gnu dot org, translation at iro dot umontreal dot ca
- Date: Wed, 18 May 2005 17:34:52 +0000 (UTC)
- Subject: Re: [PATCH] gettext support for GCC 4.0 internal format, fix for PRtranslation/21364
- References: <20050517113757.GD4930@devserv.devel.redhat.com><Pine.LNX.firstname.lastname@example.org><20050518170635.GB22344@sunsite.mff.cuni.cz>
On Wed, 18 May 2005, Jakub Jelinek wrote:
> The first patch is a patch against current GCC CVS (applies to both
> HEAD and 4.0 branch), that fixes bugs that happen in non-fuzzy strings.
> These are very serious bugs, as they usually crash the compiler, so IMHO we
> should apply this immediately, then talk to @li.org teams.
The fact is, when new .po files appear they will be committed from the TP
versions without question, whether they are manually updated ones sent to
gcc-patches by the TP Robot (I have de.po and zh_CN.po files recently sent
to the list queued to commit) or auto-updated ones merged with a new .pot
file. So changing the GCC without getting the change upstream is useless.
Whoever did that part of the "GNU CC" removal did not ensure that the
upstream version of sv.po was updated and just did a local change, which
of course got reverted when the next sv.po version appeared, so the "GNU
CC" reference in sv.po is still there; the same will happen here if you
don't get the changes upstream first.
I don't know if it's possible to send such patches to the TP directly if
the translators are not active, to ensure they don't get lost, but the
translators in question for the translations you are changing *are* active
so you should be able to get them to submit fixed versions to the TP.
> BTW, shouldn't we implement %n$ style arguments in addition to % ones?
> It seems e.g. several turkish translations relied on this...
Chiaki Ishikawa had a long patch series attempting to implement them but I
don't think they ever got in reviewable form or were following an approach
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
email@example.com (personal mail)
firstname.lastname@example.org (CodeSourcery mail)
email@example.com (Bugzilla assignments and CCs)