From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-62919-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 363 invoked by alias); 15 Apr 2009 15:33:02 -0000
Received: (qmail 347 invoked by uid 22791); 15 Apr 2009 15:33:00 -0000
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Apr 2009 15:32:51 +0000
Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KI500E00F2Y0U00@i_mtaout2.012.net.il> for gdb-patches@sources.redhat.com; Wed, 15 Apr 2009 18:32:48 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.229.34.97]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KI50031AF6NY690@i_mtaout2.012.net.il>; Wed, 15 Apr 2009 18:32:48 +0300 (IDT)
Date: Wed, 15 Apr 2009 15:33:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Configuring gdb_wchar.h
In-reply-to: <m3vdp6gdam.fsf@fleche.redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83zleikk46.fsf@gnu.org>
References: <8363hboz5x.fsf@gnu.org> <m3tz4smocb.fsf@fleche.redhat.com> <833acbo32k.fsf@gnu.org> <m3iql7jiy6.fsf@fleche.redhat.com> <83myajma7a.fsf@gnu.org> <m3ab6jjfoa.fsf@fleche.redhat.com> <83iql7m7r1.fsf@gnu.org> <m363h7je57.fsf@fleche.redhat.com> <83hc0rm1mh.fsf@gnu.org> <m3vdp6ix36.fsf@fleche.redhat.com> <8363h6mdue.fsf@gnu.org> <833acam2wl.fsf@gnu.org> <m3vdp6gdam.fsf@fleche.redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-04/txt/msg00313.txt.bz2

> Cc: gdb-patches@sources.redhat.com
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 15 Apr 2009 09:13:53 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli>     (gdb) show host-charset
> Eli>     The host character set is "auto; currently UTF-8".
> Eli>     (gdb) show target-charset
> Eli>     The target character set is "ISO-8859-1".
> 
> Eli> This is the DJGPP port.  Is this expected?  Where are these defaults
> Eli> set?
> 
> If a system has nl_langinfo(CODESET), then that is used.
> Otherwise, we fall back on a built-in default.

Would it make sense to tailor the default on specific platforms?
DJGPP does not have `nl_langinfo', and will probably never support any
character set except ASCII and the current DOS codepage.

> Eli> GDB 6.8 shows ISO-8859-1 for both character sets, FWIW.
> 
> 6.8 did no auto-detection at all and had ISO-8859-1 coded in.
> I changed the default to UTF-8 because that is increasingly common.

We need to document all that, I think.  I will give it a shot if no
one beats me to it.

Thanks.