From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27836 invoked by alias); 13 Sep 2002 18:39:48 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27829 invoked from network); 13 Sep 2002 18:39:47 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 13 Sep 2002 18:39:47 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id BEBA33C96; Fri, 13 Sep 2002 14:39:44 -0400 (EDT) Message-ID: <3D8230F0.1080104@ges.redhat.com> Date: Fri, 13 Sep 2002 11:39:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Blandy Cc: Daniel Jacobowitz , Kevin Buettner , gdb-patches@sources.redhat.com Subject: Re: [PATCH RFC] Character set support References: <1020913003056.ZM15701@localhost.localdomain> <20020913004205.GB19479@nevyn.them.org> <3D815F66.4030605@ges.redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00257.txt.bz2 > Andrew Cagney 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