This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gfortran,patch] Internationalisation of the Fortran front-end
François-Xavier Coudert <fxcoudert@gmail.com> writes:
| > Not marking them as special formats (using msgid not gmsgid) is the
| > simplest way for now.
|
| I did that, but some of the strings in the generated gcc.pot are
| marked as c-format. In fact, the strings that contains valid
| printf-style format are marked as c-formats, while those containing
| invalid printf-style format are not marked. Example:
|
| gfc_error ("Expected array subscript at %C") is marked as c-format,
| because %C is a valid printf-style format; in fact, it is used here in
| gfortran internal format to represent the current locus.
Passing locus around is specified with %H.
| gfc_error ("Iterator step at %L cannot be zero") is not marked,
| because %L is not a valid printf-style format; it is used to represent
| a locus provided as argument in gfortran.
|
| What is the solution to that? How can I get gettext not to be too clever?
You'd need to combine both styles into a single one, passing the locus
explicilty and using the %H format specifier.
|
| FX
--
Gabriel Dos Reis
gdr@integrable-solutions.net