From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: PR7580 - Command to force abort when internal error
Date: Fri, 09 Jan 2009 20:36:00 -0000 [thread overview]
Message-ID: <200901092036.24015.pedro@codesourcery.com> (raw)
In-Reply-To: <20090109182914.GM24105@adacore.com>
On Friday 09 January 2009 18:29:14, Joel Brobecker wrote:
> > > +const char internal_problem_ask[] = "ask";
> > > +const char internal_problem_yes[] = "yes";
> > > +const char internal_problem_no[] = "no";
> >
> > Don't we want these strings to be translatable? The questions we ask
> > about what to do are.
>
> I would say no. These are arguments used in a command - if we start
> translating pieces of GDB commands, I think it's going to make it harder
> for us to document the command, as well harder for the user to use it.
> For instance, some of our machines in the Paris office have system
> configuration files that force the locale to "fr". So, on these machines
> that I use only very seldomly, having to remember to use "oui" instead
> of "yes" (whereas the rest of the comment isn't translated) would
> certainly cause a certain amount of grief on my end. It also becomes
> harder to share some commands between users because every has to be
> careful of the locale...
I was going to say pretty much the same. The whole command in this case
is "maintenance set internal-error on". There doesn't seem to be any gain
in just translating the last word of it, and translating all of it, is
something I hope we're not aiming to do.
--
Pedro Alves
prev parent reply other threads:[~2009-01-09 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 3:35 Pedro Alves
2008-12-29 4:41 ` Joel Brobecker
2008-12-29 14:27 ` Pedro Alves
2008-12-31 3:57 ` Joel Brobecker
2009-01-07 21:59 ` Pedro Alves
2009-01-09 14:25 ` Eli Zaretskii
2009-01-09 15:33 ` Andreas Schwab
2009-01-09 18:16 ` Eli Zaretskii
2009-01-09 20:01 ` Andreas Schwab
2009-01-09 20:07 ` Eli Zaretskii
2009-01-09 20:15 ` Andreas Schwab
2009-01-09 20:26 ` Eli Zaretskii
2009-01-09 21:37 ` Andreas Schwab
2009-01-10 9:04 ` Eli Zaretskii
2009-01-25 23:19 ` Pedro Alves
2009-01-26 3:53 ` Eli Zaretskii
2009-01-26 16:27 ` Pedro Alves
2009-01-09 18:29 ` Joel Brobecker
2009-01-09 20:11 ` Eli Zaretskii
2009-01-10 6:34 ` Daniel Jacobowitz
2009-01-09 20:36 ` Pedro Alves [this message]
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=200901092036.24015.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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