This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [gfortran,patch] Internationalisation of the Fortran front-end
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: FX Coudert <fxcoudert at gmail dot com>
- Cc: patch <gcc-patches at gcc dot gnu dot org>, fortran at gcc dot gnu dot org
- Date: Tue, 30 Aug 2005 22:37:16 +0000 (UTC)
- Subject: Re: [gfortran,patch] Internationalisation of the Fortran front-end
- References: <4314B863.3000804@gmail.com>
On Tue, 30 Aug 2005, FX Coudert wrote:
> 1. Messages issued by gfc_error, gfc_warning and other functions
> called on constant strings are translated using the msgid convention.
> That is, developpers will not have to worry about the localization of
> such messages.
You appear to have used gmsgid for these functions so the messages are
marked as gcc-internal-format in gcc.pot. This is otherwise used for
pretty-print.c formats (with front-end extensions). Does gettext 0.14.5
understand the gfortran internal formats (so it can check translations
keep the same formats as the original message) with gcc-internal-format?
The first two lines of --version output (with version number and copyright
notice) should not be translated; only the copyright symbol should be
translated as _("(C)") so it becomes a copyright symbol in locales with
one in their character set. See other --version code for examples.
> PS: I don't know if a complete ChangeLog is needed, or if I can just
> list the files and functions and say "Added localisation support". I
> added the gcc.pot generated with maintainer mode, so that you can check
> it if you want.
A full ChangeLog would for the most part do that. There's no point in
sending gcc.pot or patches to it to the lists.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)