This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: PR7580 - Command to force abort when internal error
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Joel Brobecker <brobecker at adacore dot com>, Eli Zaretskii <eliz at gnu dot org>
- Date: Fri, 9 Jan 2009 20:36:23 +0000
- Subject: Re: PR7580 - Command to force abort when internal error
- References: <200812290335.09199.pedro@codesourcery.com> <uy6xkk146.fsf@gnu.org> <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