[gfortran,patch] Internationalisation of the Fortran front-end

[FX Coudert]

> 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.

There is no really simple solution, but a two-lines change to the 
po/exgettext script is enough. I add a new *msgid convention: function 
arguments with names ending in nocmsgid will be marked no-c-format in 
the generated POT file. I used this for internal gfortran formats.

I think I needed approval from someone with blanket write privilege.
OK for mainline? And do we want it backported to 4.0?

Built and tested on i686-linux, with maintainer mode. I did check that 
the generated POT file is similar to a one generated without the patch, 
except for the additional Fortran front-end messages.

FX
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: i18n.ChangeLog
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20050901/02c1981c/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: i18n.diff
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20050901/02c1981c/attachment-0001.ksh>