public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Wolfgang Bangerth <wolfgang.bangerth@iwr.uni-heidelberg.de>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org,
	Michel Robitaille <robitail@iro.umontreal.ca>
Subject: Re: c++/7765 [Patch]
Date: Mon, 28 Oct 2002 08:48:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.10.10210281737130.5316-100000@eris> (raw)
In-Reply-To: <20021028163245.GA24090@codesourcery.com>


Zack, Michel,

> If this weren't in the translations it would qualify as an obvious
> bugfix.  I would say, go ahead and check it in (with this change);

I can't, someone has to do that for me. Note also the changed comment in
the patch, I believe the old one had an "and" and "or" confused.

> but we need to get the fix propagated to the translation project.
> Michel, you are listed as the translator for this file.  Would you
> please incorporate these changes into the next version of the file,
> and also check for other places where the %-escapes are inconsistent
> between the msgid and the msgstr?

I'm presently about to do just that, with a small script. There are
literally dozens of such cases in the danish translation, and at least ten
more in the french one, where formats don't match (things are a little bit
complicated, since a % might be followed by a charater that needs to be
escaped in perl...). I'm surprised nobody's been paying attention to this
rather obvious problem. Also, do I understand you correctly that the
_order_ of formats needs to be preserved? (One would think so if things
are called via functions with an ellipsis at the end.) This is going to be
a headache for translators, because it restricts their choice of wording,
and it can also not be checked automatically, if the same format appears
more than once in the text.

This is probably going to be too much just for me, but once it's running,
I'd be happy to share the script.

Regards
  Wolfgang

-------------------------------------------------------------------------
Wolfgang Bangerth          email: wolfgang.bangerth@iwr.uni-heidelberg.de
                             www: http://gaia.iwr.uni-heidelberg.de/~wolf


  reply	other threads:[~2002-10-28 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28  7:43 [Patch] c++/7765 Wolfgang Bangerth
2002-10-28  8:32 ` c++/7765 [Patch] Zack Weinberg
2002-10-28  8:48   ` Wolfgang Bangerth [this message]
2002-10-28  9:59     ` Zack Weinberg
2002-10-28 10:57       ` Wolfgang Bangerth
2002-11-05  0:26         ` Kai Henningsen
2002-11-05  9:50           ` Zack Weinberg
2002-10-28 10:23   ` Joseph S. Myers

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=Pine.SOL.4.10.10210281737130.5316-100000@eris \
    --to=wolfgang.bangerth@iwr.uni-heidelberg.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=robitail@iro.umontreal.ca \
    --cc=zack@codesourcery.com \
    /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).