public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: martin@v.loewis.de (Martin v. Loewis)
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: fortran/5558: Error in POT file
Date: Fri, 01 Feb 2002 01:26:00 -0000	[thread overview]
Message-ID: <20020201092602.9968.qmail@sources.redhat.com> (raw)

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 10:20:43 +0100

 Zack Weinberg <zack@codesourcery.com> writes:
 
 > > I did not say they aren't substitution escapes, I said they are not
 > > meant for printf. Being substitution escapes is irrelevant for
 > > gettext.
 > 
 > However, they need to not get taken out just as much as printf escapes
 > do.
 
 That might well be, so there was a bug in this French
 translation. This bug is not the issue of this bug report, though.
 Michel Robitaille will mark all questionable messages as fuzzy, for
 later consideration. We should solve this problem now, before more
 translators run into the problem.
 
 > > Please consider integrating my proposed changes.
 > 
 > I tried them.  They don't do anything at all.  The generated .pot file
 > is identical with and without.
 
 What xgettext version are you using? With xgettext 0.10.40, on Linux,
 using the patch
 
 Index: lex.c
 ===================================================================
 RCS file: /cvs/gcc/egcs/gcc/f/lex.c,v
 retrieving revision 1.31
 diff -u -r1.31 lex.c
 --- lex.c	2002/01/02 23:18:57	1.31
 +++ lex.c	2002/02/01 08:34:18
 @@ -424,6 +424,7 @@
  		   && ((1 << (TYPE_PRECISION (integer_type_node) - (count - 1) * 4))
  		       <= (int) firstdig)))
  	{
 +	  /* xgettext:no-c-format */
  	  ffebad_start_msg_lex ("Hex escape at %0 out of range",
  				FFEBAD_severityPEDANTIC);
  	  ffelex_bad_here_ (0, line, column);
 @@ -457,6 +458,7 @@
        && TYPE_PRECISION (char_type_node) < HOST_BITS_PER_INT
        && code >= (1 << TYPE_PRECISION (char_type_node)))
      {
 +      /* xgettext:no-c-format */
        ffebad_start_msg_lex ("Escape sequence at %0 out of range for character",
  			    FFEBAD_severityFATAL);
        ffelex_bad_here_ (0, line, column);
 
 I get a template containing
 
 #: f/lex.c:428
 #, no-c-format
 msgid "Hex escape at %0 out of range"
 msgstr ""
 
 #: f/lex.c:462
 #, no-c-format
 msgid "Escape sequence at %0 out of range for character"
 msgstr ""
 
 Notice how c-format has been replaced with no-c-format.
 
 > I was not aware that this was the case - and the Turkish translator
 > had a similar problem, reported that removing the c-format marker
 > solved it, and has had no trouble uploading.
 
 In those cases (e.g. config/m88k/m88k.c:3063), msgfmt accepts the
 translation even with c-format (%C is taken as the wchar_t
 format). Therefore, the translator did not need to remove the c-format
 markers, and the robot accepted the translation since msgfmt found no
 errors even after putting them back in.
 
 Regards,
 Martin


             reply	other threads:[~2002-02-01  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  1:26 Martin v. Loewis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 15:29 pthomas
2002-02-01 16:16 Martin v. Loewis
2002-02-01 15:06 Philipp Thomas
2002-02-01 14:56 Toon Moene
2002-02-01 13:56 Philipp Thomas
2002-02-01 13:26 Toon Moene
2002-02-01  6:16 Philipp Thomas
2002-02-01  6:09 toon
2002-01-31 17:06 Zack Weinberg
2002-01-31 16:36 Martin v. Loewis
2002-01-31 15:56 Zack Weinberg
2002-01-31 13:06 martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020201092602.9968.qmail@sources.redhat.com \
    --to=martin@v.loewis.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).