From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7794 invoked by alias); 13 Sep 2002 19:15:43 -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 7787 invoked from network); 13 Sep 2002 19:15:42 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 13 Sep 2002 19:15:42 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17pwqr-0002Y1-00; Fri, 13 Sep 2002 15:15:42 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17pvv3-0000ut-00; Fri, 13 Sep 2002 15:15:57 -0400 Date: Fri, 13 Sep 2002 12:15:00 -0000 From: Daniel Jacobowitz To: Kevin Buettner Cc: Andrew Cagney , Jim Blandy , gdb-patches@sources.redhat.com Subject: Re: [PATCH RFC] Character set support Message-ID: <20020913191557.GA3392@nevyn.them.org> Mail-Followup-To: Kevin Buettner , Andrew Cagney , Jim Blandy , gdb-patches@sources.redhat.com References: <1020913003056.ZM15701@localhost.localdomain> <20020913004205.GB19479@nevyn.them.org> <20020913140312.GA10942@nevyn.them.org> <20020913173351.GA25544@nevyn.them.org> <3D823193.3020708@ges.redhat.com> <1020913191142.ZM19189@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1020913191142.ZM19189@localhost.localdomain> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-09/txt/msg00261.txt.bz2 On Fri, Sep 13, 2002 at 12:11:42PM -0700, Kevin Buettner wrote: > On Sep 13, 2:42pm, Andrew Cagney wrote: > > > > On Fri, Sep 13, 2002 at 12:02:29PM -0500, Jim Blandy wrote: > > > > > >> Daniel Jacobowitz writes: > > > > > >> > I'm not suggesting reading wchar_t's from the target; that's not > > >> > terribly useful a thing to do. You _want_ the host wchar_t. It is > > >> > a host type capable of holding a wide character; the type changes > > >> > based on platform and on whether or not the platform actually has > > >> > wide character support. > > > > > >> If you're suggesting using the host's wchar_t to hold characters after > > >> conversion from the target charset to the host charset, then I'm with > > >> you. > > >> > > >> If you're suggesting using the host's wchar_t to hold character values > > >> that have been read from the target, but not yet converted to the > > >> host's charset, then I really disagree. The target's wchar_t could be > > >> 32 bits, while the host's might be 16 bits. > > > > > > Precisely. I was suggesting using host wchar_t after conversion to > > > host format. > > > > Sounds like we need a WCHAREST :-) > > Yes, or something equivalent. > > What I'd like to determine is whether Daniel thinks that the notion of > a wchar_t *must* be added to Jim's work before the patch can go in. > (IMO, the wchar_t changes should be done as an incremental improvement.) Certainly not; sorry if I gave that impression. I think we should take it as-is now, and then try to find someone with better i18n experience to make it multibyte-friendly; Debian usually has an excess of such people, so I'll go looking later :) -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer