fortran/5558: Error in POT file

[Martin v. Loewis]

The following reply was made to PR fortran/5558; it has been noted by GNATS.

From: martin@v.loewis.de (Martin v. Loewis)
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: fortran/5558: Error in POT file
Date: 01 Feb 2002 01:30:34 +0100

 Zack Weinberg <zack@codesourcery.com> writes:
 
 > You are mistaken.  Those %0's most definitely are substitution
 > escapes.  They are not the same as printf substitutions, but they
 > are substitutions nonetheless.
 
 I did not say they aren't substitution escapes, I said they are not
 meant for printf. Being substitution escapes is irrelevant for
 gettext.
 
 > Having said that, I can see the problem - it thinks the escape is 
 > "%0 o" instead of just "%0".  Your fix is to remove the "#, c-format"
 > annotation.
 
 Please consider integrating my proposed changes. It is a plain bug in
 gcc that the provided catalog includes the c-format markup. This
 c-format is put in by your invocation of xgettext, so I would argue
 that it is your job to remove it. xgettext provides the mechanism to
 do this automatically (instead of doing it manually after each
 extraction), so please use them.
 
 > The second translation needs to have "%0" in it somewhere analogous to
 > where it appears in the English, or the error messages will not make
 > sense in context.
 
 Well, that would be then an error in the translation. There are many
 ways to deal with those; perhaps the best way (given the current
 tools) is to put a comment for the translators into the catalog that
 the %0 escape must occur in the translated message. If you want to
 create a custom to to perform this check automatically, that would be
 fine as well.
 
 > I am attempting to get a more flexible mechanism for format-string
 > handling put into gettext, but Bruno so far refuses to even consider
 > it.
 
 Please don't use the gcc catalog as a weapon in your fight with
 Bruno. Instead, please incorporate the requested changes, so that
 translators have a chance to submit their translations (the robot will
 reject submissions if translators have removed c-format markers; this
 was necessary to avoid security risks resulting from buffer overruns).
 
 Regards,
 Martin