Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: i18n, part 2
Date: Mon, 06 Dec 2004 23:04:00 -0000	[thread overview]
Message-ID: <20041206155114.6bab8d59.kevinb@redhat.com> (raw)
In-Reply-To: <01c4dbd5$Blat.v2.2.2$98515300@zahav.net.il>

On Mon, 06 Dec 2004 22:52:06 +0200
"Eli Zaretskii" <eliz@gnu.org> wrote:

> > Date: Mon, 6 Dec 2004 10:39:30 -0700
> > From: Kevin Buettner <kevinb@redhat.com>
> > Cc: gdb-patches@sources.redhat.com
> > 
> > On Sat, 4 Dec 2004 20:57:02 +0100
> > Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr> wrote:
> > 
> > > * aix-thread.c:aix_thread_extra_thread_info()
> > > 
> > >   "tid %d, %s" doesn't add much context to ", suspended". Besides,
> > >   splitting the execution flow with if (tid != PTHDB_INVALID_TID) would
> > >   not be identical to the current code. That is why I left the code as
> > >   is.
> > 
> > Seems reasonable.
> 
> Excuse me, but in what language is this ``reasonable''?  In any
> language where ``suspended'' needs to be modified according to the
> gender (masculine, feminine, etc.) of the corresponding noun, the
> translator will have no hope of getting the translation right without
> reading the code and understanding what it does.  So much for
> ``reasonable''.

The code in question is simply outputting a list of attributes
associated with a particular thread.  How should we make the necessary
context available to the translator without putting an undue burden
on GDB maintainers?  What do other projects do in this regard?

Kevin


  reply	other threads:[~2004-12-06 22:51 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
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 [this message]
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=20041206155114.6bab8d59.kevinb@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.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