Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason Molenda <jmolenda@apple.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com, Daniel Jacobowitz <drow@false.org>
Subject: Re: [rfc] Bug fixes for CLI "show" command
Date: Wed, 21 Apr 2004 21:48:00 -0000	[thread overview]
Message-ID: <8CADE7C7-93DD-11D8-89EF-000A9569836A@apple.com> (raw)
In-Reply-To: <40855F1E.9080906@gnu.org>

Hi Andrew,

On Apr 20, 2004, at 10:34 AM, Andrew Cagney wrote:

>> -	  ui_out_field_string (uiout, "prefix", list->prefixname + 5);
>> -	  cmd_show_list (*list->prefixlist, from_tty, list->prefixname + 5);
>> +	  char *new_prefix = strstr (list->prefixname, "show ") + 5;
>
> This is no better - i18n.

I don't understand - is there actual intention to internationalize the 
gdb commands themselves?  When we talk about i18n'ing gdb, my reaction 
would be internationalizing the _output messages_ -- the errors, the 
warnings, the help text.  Do you mean to say that it's a goal of yours 
to support something like

(gdb) 表示environment

in place of "show environment".  Or 「(gdb) 表示環境」 (which is just painful 
to the eye in either language :-) to make it all Japanese.

Just MHO, but internationalizing the actual gdb commands is not 
particularly helpful for non-English native speakers.  
Internationalizing help/warning/errors would be very useful for them.  
Am I misunderstanding Daniel's patch?

Jason


  parent reply	other threads:[~2004-04-21 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 20:00 Daniel Jacobowitz
2004-04-21 14:55 ` Andrew Cagney
2004-04-21 14:59   ` Daniel Jacobowitz
2004-04-21 15:49     ` Andrew Cagney
2004-04-21 15:53       ` Daniel Jacobowitz
2004-04-21 18:39         ` Eli Zaretskii
2004-04-21 19:26           ` Andrew Cagney
2004-04-21 21:48   ` Jason Molenda [this message]
2004-04-21 22:22     ` Andrew Cagney
2004-05-10 18:17 ` Daniel Jacobowitz

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=8CADE7C7-93DD-11D8-89EF-000A9569836A@apple.com \
    --to=jmolenda@apple.com \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --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