From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>,
gdb-patches@sources.redhat.com
Subject: Re: i18n, part 2
Date: Sun, 05 Dec 2004 23:39:00 -0000 [thread overview]
Message-ID: <20041205214115.GA24180@nevyn.them.org> (raw)
In-Reply-To: <01c4db12$Blat.v2.2.2$4dfdf600@zahav.net.il>
On Sun, Dec 05, 2004 at 11:34:10PM +0200, Eli Zaretskii wrote:
> This code produces a complete sentence one word at a time, which I
> think is bad for translating. I think the code needs to be rewritten
> to have full sentences like these:
>
> "tid %d, %s, suspended, detached, cancel pending"
> "tid %d, %s, detached, cancel pending"
> "tid %d, %s, cancel pending"
> "tid %d, %s"
> "tid %d, %s, suspended, cancel pending"
> "tid %d, %s, suspended, detached"
> "tid %d, %s, detached, cancel pending"
> "tid %d, %s, detached"
>
> etc. That makes the code less clever, but the translation is much
> easier. As the code is now, it will be almost impossible to get right
> in some languages.
Yuck! What if someone wants to add another status? I understand that
there is a translation problem here, but I find it really hard to
accept that enumerating exponential combinations is really the
solution. I suspect either:
- the message needs to be redesigned in some more friendly way
- we need a more friendly way to output a list of translated statuses
- or else we need to leave the status message untranslated pending
some thought on the above.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-05 21:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 20:06 Baurjan Ismagulov
2004-12-04 21:52 ` Daniel Jacobowitz
2004-12-04 22:17 ` Baurjan Ismagulov
2004-12-04 23:59 ` Daniel Jacobowitz
2004-12-05 21:41 ` Eli Zaretskii
2004-12-05 23:39 ` Daniel Jacobowitz [this message]
2004-12-06 2:19 ` Baurjan Ismagulov
2004-12-06 4:59 ` Eli Zaretskii
2004-12-06 0:00 ` Baurjan Ismagulov
2004-12-15 0:50 ` Baurjan Ismagulov
2004-12-15 21:48 ` Eli Zaretskii
2004-12-06 18:53 ` Kevin Buettner
2004-12-06 20:59 ` Eli Zaretskii
2004-12-06 23:04 ` Kevin Buettner
2004-12-07 5:08 ` Eli Zaretskii
2004-12-07 5:10 ` Daniel Jacobowitz
2004-12-07 17:28 ` Kevin Buettner
2004-12-07 19:59 ` Eli Zaretskii
2004-12-07 20:28 ` Andreas Schwab
2004-12-12 19:50 ` Andrew Cagney
2004-12-12 22:08 ` Eli Zaretskii
2004-12-12 18:23 ` Andrew Cagney
2004-12-12 21:49 ` Eli Zaretskii
2004-12-07 22:02 ` Eli Zaretskii
2004-12-12 18:35 ` Andrew Cagney
2004-12-26 4:46 ` Baurjan Ismagulov
2004-12-26 23:25 ` Eli Zaretskii
2005-01-05 15:48 ` Andrew Cagney
2005-01-05 16:07 ` 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=20041205214115.GA24180@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.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