3.0 branch: POTFILES.in broken

[Joseph S. Myers]

On 12 Jun 2001, Tom Tromey wrote:

> The Java front end will need actual hacking before translation can
> commence.  There is a lot of code that computes too much of the
> string, eg:
>
>       parse_error_context (wfl,
> 			   "Can't access %s %s `%s.%s' from `%s'",
> 			   access, what, klass, fct_name, refklass);
>
> In this example only `what' is a problem, I think.  Anyway, an
> extensive code review will be needed :-(

When rewriting parts of the format checking code, I wondered whether some
of the uses there might pose i18n problems, e.g.

                status_warning (status, "%s ignored with %s in %s format",
                                _(s->name), _(t->name), fki->name);

The first two names here are such things as "precision" or "length
modifier" (the third is something like "printf" to which i18n doesn't
apply).  If the translations of these words get declined differently in
different places in the sentence or in different warning messages, there
would be the problem of providing a single translation of "precision" that
works in all places.  I don't know whether e.g. ngettext could be misused
if this problem arises.

-- 
Joseph S. Myers
jsm28@cam.ac.uk