Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Schlie <schlie@comcast.net>
To: Andrew Cagney <cagney@gnu.org>, Eli Zaretskii <eliz@gnu.org>
Cc: <gdb@sources.redhat.com>
Subject: Re: GDB 6.4 and translations
Date: Thu, 04 Nov 2004 16:55:00 -0000	[thread overview]
Message-ID: <BDAFC922.7C4E%schlie@comcast.net> (raw)
In-Reply-To: <418A4BDE.6050302@gnu.org>

> From: Andrew Cagney <cagney@gnu.org>
> 
> Eli Zaretskii wrote:
>>> 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.
> 
> Yep, huh?  Can someone please post a concrete example of what this is
> all about?
> 
> Andrew

Basically GCC 4.0 has tentatively adopted a convention to allow the
specification of a quoted format specifier something basically like:

 printf("quoted %qX" some_value) => quoted "123", for example.

Which I is arguably cleaner then attempting to escape embedded quotes
within format strings; but has then further chose to hard code the
generation of Unicode left/right typographical quote characters in lieu
of vanilla ASCII quote characters by default if the local environment
variable indicates that Unicode is supported, which may be taking
things too far, see: http://gcc.gnu.org/ml/gcc/2004-10/msg01271.html

(but the good news is that it may be relatively easily overridden by
modifying local environment variables seen by GCC prior to being invoked)




  reply	other threads:[~2004-11-04 16:55 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
2004-11-04 15:34   ` Andrew Cagney
2004-11-04 16:55     ` Paul Schlie [this message]
  -- 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=BDAFC922.7C4E%schlie@comcast.net \
    --to=schlie@comcast.net \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb@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