From: "Eli Zaretskii" <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: schlie@comcast.net, gdb@sources.redhat.com
Subject: Re: GDB 6.4 and translations
Date: Thu, 04 Nov 2004 21:35:00 -0000 [thread overview]
Message-ID: <01c4c2b5$Blat.v2.2.2$91ae39c0@zahav.net.il> (raw)
In-Reply-To: <20041104152243.GA28361@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 4 Nov 2004 10:22:43 -0500)
> Date: Thu, 4 Nov 2004 10:22:43 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
>
> Eli, the background is that GCC has adopted a new mechanism (the 'q'
> qualifier to its internal diagnostics machinery, which takes
> printf-like formats). This allows GCC to output Unicode quotes when
> using the untranslated (i.e. English) messages - if the current locale
> supports them.
Thanks for explaining this.
FWIW, I think GCC guys were too quick to assume that UTF-8 locales are
good enough for this to be the default, but I agree that the fix is
easy enough for users who bump into this problem.
> People do still parse the CLI. They will no matter what we tell them.
> Well, it's never been intended as a machine parseable interface
That's true, but I think that some use of CLI is inevitable even if
the front end uses MI as its main protocol. However, I think that a
front end should set LC_MESSAGES=C before invoking an inferior GDB (or
perhaps GDB should do this internally when invoked with -interp=mi?),
and we should be careful not to translate any string printed by MI.
next prev parent reply other threads:[~2004-11-04 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 0:27 Paul Schlie
2004-11-04 4:52 ` Eli Zaretskii
2004-11-04 5:52 ` Paul Schlie
2004-11-04 8:11 ` Fabian Cenedese
2004-11-04 15:22 ` Daniel Jacobowitz
2004-11-04 16:21 ` Paul Schlie
2004-11-04 21:35 ` Eli Zaretskii [this message]
2004-11-04 15:34 ` Andrew Cagney
2004-11-04 16:55 ` Paul Schlie
-- strict thread matches above, loose matches on Subject: below --
2004-11-03 22:02 Andrew Cagney
2004-11-04 4:39 ` Eli Zaretskii
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='01c4c2b5$Blat.v2.2.2$91ae39c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=schlie@comcast.net \
/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