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: c++/7084: locale dependant ICE
Date: Fri, 21 Jun 2002 01:36:00 -0000	[thread overview]
Message-ID: <20020621082603.13819.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7084; it has been noted by GNATS.

From: martin@v.loewis.de (Martin v. Loewis)
To: Zack Weinberg <zack@codesourcery.com>
Cc: fasbjx@free.fr, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
   debian-gcc@lists.debian.org, robitail@IRO.UMontreal.CA
Subject: Re: c++/7084: locale dependant ICE
Date: 21 Jun 2002 10:19:46 +0200

 I'm forwarding this to the French translator, Michel Robitaille.
 Michel, can you please correct these errors and submit a new catalog?
 
 > This would be a bug in fr.po:
 >=20
 > | #: cp/call.c:2834
 > | msgid "%s for `%T %s' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%T %s=C2=BB"
 > |
 > | #: cp/call.c:2837
 > | msgid "%s for `%T [%T]' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%T [%T]=C2=BB"
 > |
 > | #: cp/call.c:2842
 > | msgid "%s for `%T %s %T' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%t [%T]=C2=BB"
 > |
 > | #: cp/call.c:2845
 > | msgid "%s for `%s %T' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%t [%T]=C2=BB"
 >=20
 > You will notice that the translations do not match the messages, and
 > that the escape sequences are wrong: in particular, a %t has
 > appeared.  This is not a defined %-escape, so we abort in the middle
 > of generating the error message, which triggers the "r=C2=8E=C3=A9-ent=C2=
 =8E=C3=A9e" message.
 >=20
 > Correct entries, presumably, would read
 >=20
 > | #: cp/call.c:2834
 > | msgid "%s for `%T %s' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%T %s=C2=BB"
 > |
 > | #: cp/call.c:2837
 > | msgid "%s for `%T [%T]' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%T [%T]=C2=BB"
 > |
 > | #: cp/call.c:2842
 > | msgid "%s for `%T %s %T' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%T %s %T=C2=BB"
 > |
 > | #: cp/call.c:2845
 > | msgid "%s for `%s %T' operator"
 > | msgstr "%s pour l'op=C3=A9rateur =C2=AB%s %T=C2=BB"
 >=20
 > I am not sure what the protocol is for fixing such bugs.  The
 > corrections need to make it back to the translation project somehow,
 > and the .po files need to be audited for other occurrences of this
 > problem (why didn't msgfmt bitch?)
 
 Because the messages are not marked c-format, and use format
 specifiers that are not supported in C. I think the only option is to
 implement a custom checker, as a post processor.
 
 Regards,
 Martin


             reply	other threads:[~2002-06-21  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21  1:36 Martin v. Loewis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 11:35 bangerth
2002-10-03  7:39 lerdsuwa
2002-06-20 20:06 Zack Weinberg
2002-06-20  4:56 fasbjx

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=20020621082603.13819.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).