Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Kevin Buettner <kevinb@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] Character set support
Date: Fri, 13 Sep 2002 11:39:00 -0000	[thread overview]
Message-ID: <3D8230F0.1080104@ges.redhat.com> (raw)
In-Reply-To: <vt2r8fxvnmh.fsf@zenia.red-bean.com>

> Andrew Cagney <ac131313@ges.redhat.com> writes:
> 
>> >    At the moment, GDB only supports single-byte, stateless character
>> >    sets.  This includes the ISO-8859 family (ASCII extended with
>> >    accented characters, and (I think) Cyrillic, for European
>> >    languages), and the EBCDIC family (used on IBM's mainframes).
>> >    Unfortunately, it excludes many Asian scripts, the fixed- and
>> >    variable-width Unicode encodings, and other desireable things.
>> >    Patches are welcome!  (For example, it would be nice if the Java
>> >    string support could simply get absorbed into some more general
>> >    multi-byte encoding support.)
> 
>> 
>> I think this should be mentioned in the documentation.
> 
> 
> The user documentation explicitly lists all the character sets that
> are supported.  There's nothing in the user interface that reveals the
> implementation's restrictions.  Whether GDB is prepared internally to
> handle others doesn't belong in the user docs, it seems to me.

I think it is also important to set the users expectations.  If 
expressed right it may even encourage a reader to try to remove the 
restriction.

enjoy,
Andrew



  reply	other threads:[~2002-09-13 18:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 17:31 Kevin Buettner
2002-09-12 17:41 ` Daniel Jacobowitz
2002-09-12 20:24   ` Jim Blandy
2002-09-12 20:45     ` Andrew Cagney
2002-09-13 10:05       ` Jim Blandy
2002-09-13 11:39         ` Andrew Cagney [this message]
2002-09-13 19:06           ` Jim Blandy
2002-09-16 22:25             ` Andrew Cagney
2002-09-19 12:52               ` Jim Blandy
2002-09-19 13:27                 ` Kevin Buettner
2002-09-20 13:49                   ` Eli Zaretskii
2002-09-13  7:02     ` Daniel Jacobowitz
2002-09-13 10:16       ` Jim Blandy
2002-09-13 10:33         ` Daniel Jacobowitz
2002-09-13 11:42           ` Andrew Cagney
2002-09-13 12:11             ` Kevin Buettner
2002-09-13 12:15               ` Daniel Jacobowitz
2002-09-12 17:53 ` Andrew Cagney
2002-09-12 18:08   ` Kevin Buettner
2002-09-19 17:36 ` Kevin Buettner
2002-09-19 17:46   ` Kevin Buettner
2002-09-19 18:12   ` Andrew Cagney
2002-09-20  0:12     ` Kevin Buettner
2002-09-20  9:08       ` Andrew Cagney
2002-09-20 14:58         ` Kevin Buettner
2002-09-20 16:33           ` Andrew Cagney
2002-09-21  1:26           ` Eli Zaretskii
2002-09-20 16:55         ` Kevin Buettner
2002-09-20  8:59 ` Eli Zaretskii
2002-09-20 17:34   ` Kevin Buettner

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=3D8230F0.1080104@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=kevinb@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