This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: 3.0 branch: POTFILES.in broken
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: 3.0 branch: POTFILES.in broken
- From: Tom Tromey <tromey at redhat dot com>
- Date: 12 Jun 2001 11:45:59 -0600
- Cc: Zack Weinberg <zackw at Stanford dot EDU>, Dennis Bjorklund <db at zigo dot dhs dot org>, Mark Mitchell <mark at codesourcery dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- References: <Pine.SOL.4.33.0106121759290.21852-100000@red.csi.cam.ac.uk>
- Reply-To: tromey at redhat dot com
>>>>> "Joseph" == Joseph S Myers <jsm28@cam.ac.uk> writes:
Joseph> When rewriting parts of the format checking code, I wondered
Joseph> whether some of the uses there might pose i18n problems, e.g.
I think so.
Joseph> The first two names here are such things as "precision" or
Joseph> "length modifier" (the third is something like "printf" to
Joseph> which i18n doesn't apply). If the translations of these words
Joseph> get declined differently in different places in the sentence
Joseph> or in different warning messages, there would be the problem
Joseph> of providing a single translation of "precision" that works in
Joseph> all places. I don't know whether e.g. ngettext could be
Joseph> misused if this problem arises.
In general it is probably better to just rewrite the code.
Uli wrote a paper describing the various problems one might
encounter here. I forget where it is though.
Another problem with this approach, beyond declensions and the like,
is that it is still hard for a translator: in the PO file there will
be a string like `%s ignored with %s in %s format', and then somewhere
else there will be `length modifier'. The difficulty arises when the
translator isn't easily able to discover that these two phrases are
related.
Tom