From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: ibr@ata.cs.hun.edu.tr, gdb-patches@sources.redhat.com
Subject: Re: an i18n sample
Date: Mon, 25 Oct 2004 20:10:00 -0000 [thread overview]
Message-ID: <01c4bace$Blat.v2.2.2$09c744a0@zahav.net.il> (raw)
In-Reply-To: <20041024201802.GA17380@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 24 Oct 2004 16:18:02 -0400)
> Date: Sun, 24 Oct 2004 16:18:02 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>,
> gdb-patches@sources.redhat.com
>
> I agree about partial translations, of course. In this particular
> case, it looks like the file needs type_sprint or type_to_string.
It is generally bad to produce strings in parts, because that prevents
the translator from seing the full sentence or at least a full phrase.
So I think type_sprint etc. will not solve the problem I was worried
about.
> > > if (TYPE_LENGTH (type) <= 0)
> > > {
> > > - warning ("Invalid type size for `%s' detected: %d.",
> > > - TYPE_NAME (rtype) ? TYPE_NAME (rtype) : "<unnamed>",
> > > + warning (_("Invalid type size for `%s' detected: %d."),
> > > + TYPE_NAME (rtype) ? TYPE_NAME (rtype) : _("<unnamed>"),
> > > TYPE_LENGTH (type));
> > > }
> >
> > Same here.
>
> Actually, I disagree about this one. Whether or not "<unnamed>"
> should be translated, is there any reason not to translate the format
> string?
That's not what I meant. I wanted to see something like this:
if (TYPE_LENGTH (type) <= 0)
{
if (TYPE_NAME (rtype))
warning (_("Invalid type size for `%s' detected: %d."),
TYPE_NAME (rtype), TYPE_LENGTH (type));
else
warning (_("Invalid type size for <unnamed> detected: %d."),
TYPE_LENGTH (type));
}
> That said, the "when" is a partial sentence, and the \n%*s doesn't
> need to be translated.
That's a very partial sentence, so it needs to be made a full sentence
along the same lines as above.
next prev parent reply other threads:[~2004-10-25 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 10:45 Baurjan Ismagulov
2004-10-24 19:28 ` Eli Zaretskii
2004-10-24 19:57 ` Baurjan Ismagulov
2004-10-24 20:18 ` Daniel Jacobowitz
2004-10-25 20:10 ` Eli Zaretskii [this message]
2004-10-25 20:20 ` Daniel Jacobowitz
2004-10-26 4:47 ` Eli Zaretskii
2004-10-26 20:02 ` Daniel Jacobowitz
2004-10-27 5:03 ` Eli Zaretskii
2004-10-25 21:59 ` Andrew Cagney
2004-10-26 5:02 ` Eli Zaretskii
2004-10-26 7:54 ` Baurjan Ismagulov
2004-10-26 19:56 ` Eli Zaretskii
2004-10-27 17:28 ` Andrew Cagney
2004-11-27 20:54 ` Baurjan Ismagulov
2004-11-27 22:18 ` Eli Zaretskii
2004-11-27 22:54 ` Baurjan Ismagulov
2004-12-04 19:55 ` Baurjan Ismagulov
2004-12-04 22:31 ` Baurjan Ismagulov
2004-12-12 17:12 ` Andrew Cagney
2004-12-12 18:42 ` Daniel Jacobowitz
2004-12-12 21:07 ` Andrew Cagney
2004-12-13 3:37 ` Eli Zaretskii
2004-12-04 23:04 ` Eli Zaretskii
2004-12-05 23:46 ` Baurjan Ismagulov
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='01c4bace$Blat.v2.2.2$09c744a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ibr@ata.cs.hun.edu.tr \
/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