From: Daniel Jacobowitz <drow@false.org>
To: Paul Schlie <schlie@comcast.net>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sources.redhat.com
Subject: Re: GDB 6.4 and translations
Date: Thu, 04 Nov 2004 15:22:00 -0000 [thread overview]
Message-ID: <20041104152243.GA28361@nevyn.them.org> (raw)
In-Reply-To: <BDAF2DDB.7C2F%schlie@comcast.net>
On Thu, Nov 04, 2004 at 12:52:43AM -0500, Paul Schlie wrote:
> No, I don't think you're missing anything. I was simply speculating, being
> ignorant of GDB's longer term internationalization plans, that it may be
> wise to try to avoid the potential complications associated with the default
> use of Unicode left/right quote character codes as tentatively chosen to be
> used in GCC 4.0 quoted output message text on unicode supported platforms;
> as although it may seem aesthetically pleasant, it's likely to create
> otherwise unnecessary complications in circumstances where interface,
> status, warning, and/or error messages may be parsed by subsequent tools
> which may not be unicode aware.
And I think you're just as wrong here as you were when you said this on
the GCC list.
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. A user with UTF-8 locales and non-UTF-8 terminals
complained, and Paul also objected on machine-parseability grounds. So
fix your locale and move on... I think the nicety of providing the
quote characters the user's locale requested is a very nice touch.
> Where given your statements, it doesn't seem to be part of GDB's present
> plans, which I suspect is good; but still suspect that any translated
> message text containing ASCII symbols which are anticipated to be
> potentially utilized by other programs for whatever purpose, should likely
> retain the original ASCII symbol codes in the text were possible by default
> (even on Unicode platforms) to prevent potential subsequent complications,
> if there's a choice in the matter.
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
what MI is for nowadays), so if they have to add locale workarounds I'm
entirely unsympathetic.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-04 15:22 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 [this message]
2004-11-04 16:21 ` Paul Schlie
2004-11-04 21:35 ` Eli Zaretskii
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=20041104152243.GA28361@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.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