public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Paul Schlie <schlie@comcast.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.4 and translations
Date: Thu, 04 Nov 2004 04:52:00 -0000	[thread overview]
Message-ID: <01c4c229$Blat.v2.2.2$72d18d40@zahav.net.il> (raw)
In-Reply-To: <BDAEE197.7C21%schlie@comcast.net> (message from Paul Schlie on Wed, 03 Nov 2004 19:27:19 -0500)

> Date: Wed, 03 Nov 2004 19:27:19 -0500
> From: Paul Schlie <schlie@comcast.net>
> 
> Although I don't know if it's been considered or even an issue, but it may
> be worth trying to avoid the use of Unicode's typographical quote characters
> in otherwise ASCII message string output on even Unicode supported platforms
> by default

Sorry, I have no idea what you are talking about; please consider
elaborating, e.g., by providing an example of such a problematic
message.

AFAIK, we don't use any non-ASCII characters in the GDB message text.
If you know about any use of such characters in GDB, please point out
where in the code we have them, since I believe that must be some bug.

As for the translated messages, it's entirely up to the translators'
teams to decide how they encode the text in their language.  If they
decide to use UTF-8 or some other Unicode encoding (and use Unicode
quoting characters), there's no way we could prevent them from doing
so.  Nor do I think we should: the translators know better than we do
what characters are supported by end-user platforms in their locale.

> especially for text which may likely be subsequently parsed by tools likely
> benefiting, and/or depending on the use of plain old ASCII quote characters.

If you are talking about GDB GUI front ends, they should invoke GDB
after setting the Posix locale anyway, since they want the messages in
English to be able to parse them.  THus, if the original messages we
have in the code are in plain ASCII, the front ends will not have any
problems here.

Or did I miss something?

  reply	other threads:[~2004-11-04  4:52 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 [this message]
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
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='01c4c229$Blat.v2.2.2$72d18d40@zahav.net.il' \
    --to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).