This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why doesn't gcc.pot use gcc-internal-format?
- 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>, Zack Weinberg <zack at codesourcery dot com>, gcc at gcc dot gnu dot org
- Date: Tue, 17 May 2005 13:46:30 +0000 (UTC)
- Subject: Re: Why doesn't gcc.pot use gcc-internal-format?
- References: <20050517113757.GD4930@devserv.devel.redhat.com>
On Tue, 17 May 2005, Jakub Jelinek wrote:
> Bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21364
> shows that it is very dangerous to not check format strings
> in translations. No translation of a particular message is always
> better than a bad translation that causes compiler crash.
>
> Now, looking at gettext, it seems to support GCC internal
> message format, although older one (3.3.x - it doesn't grok e.g. %J,
> q, ll and w format flags, %<, %>, %').
>
> exgettext would probably need to pass --flag options in $kopt
> (not sure if that needs to be in addition to --keyword or in addition to).
Once there's a gettext release supporting GCC 4 formats (NB that %' is a
format which is not expected to appear in the translated messages, only
the untranslated ones, and as %< %> %' don't format any arguments it
doesn't really matter whether they match in translated/untranslated
formats; they can be handled like %%), I see no problem with updating
install.texi regarding the required gettext version, patching exgettext
(mainline and 4.0) and regenerating gcc.pot.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)