Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Configuring gdb_wchar.h
Date: Wed, 15 Apr 2009 18:04:00 -0000	[thread overview]
Message-ID: <m34owphjzm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83zleikk46.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 15 Apr 2009 18\:32\:57 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Tom> If a system has nl_langinfo(CODESET), then that is used.
Tom> Otherwise, we fall back on a built-in default.

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

Yeah, it would make sense to be able to auto-select the host charset.
If there is a way to detect the current DOS codepage, and if that is
equivalent to the notion of the host charset (I don't know), then we
could put the needed code into _initialize_charset.

Eli> GDB 6.8 shows ISO-8859-1 for both character sets, FWIW.

Tom> 6.8 did no auto-detection at all and had ISO-8859-1 coded in.
Tom> I changed the default to UTF-8 because that is increasingly common.

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

How about the appended?

Tom

2009-04-15  Tom Tromey  <tromey@redhat.com>

	* gdb.texinfo (Character Sets): Document default character set.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 5269dfc..ebba32f 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -7998,7 +7998,9 @@ Set the current host character set to @var{charset}.
 
 By default, @value{GDBN} uses a host character set appropriate to the
 system it is running on; you can override that default using the
-@code{set host-charset} command.
+@code{set host-charset} command.  On some systems, @value{GDBN} cannot
+automatically determine the appropriate host character set.  In this
+case, @value{GDBN} uses @samp{UTF-8}.
 
 @value{GDBN} can only use certain character sets as its host character
 set.  If you type @kbd{@w{set target-charset @key{TAB}@key{TAB}}},


  reply	other threads:[~2009-04-15 18:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 17:53 Eli Zaretskii
2009-04-13 17:54 ` Tom Tromey
2009-04-14 12:03   ` Eli Zaretskii
2009-04-14 16:31     ` Tom Tromey
2009-04-14 17:11       ` Eli Zaretskii
2009-04-14 17:42         ` Tom Tromey
2009-04-14 18:04           ` Eli Zaretskii
2009-04-14 18:15             ` Tom Tromey
2009-04-14 20:17               ` Eli Zaretskii
2009-04-15  0:23                 ` Tom Tromey
2009-04-15 10:06                   ` Eli Zaretskii
2009-04-15 14:01                     ` Eli Zaretskii
2009-04-15 15:14                       ` Tom Tromey
2009-04-15 15:33                         ` Eli Zaretskii
2009-04-15 18:04                           ` Tom Tromey [this message]
2009-04-15 19:20                             ` Eli Zaretskii
2009-04-15 19:53                               ` Tom Tromey
2009-04-15 20:18                                 ` Eli Zaretskii
2009-04-18  9:47                                   ` Eli Zaretskii
2009-04-18 17:28                                     ` Tom Tromey
2009-04-19 18:30                                       ` Eli Zaretskii
2009-04-15 15:08                     ` Tom Tromey
2009-04-15 15:12                       ` Pedro Alves
2009-04-15 15:26                         ` Tom Tromey
2009-04-15 15:47                       ` Eli Zaretskii
2009-04-15 18:07                         ` Tom Tromey
2009-04-15 22:13                   ` Tom Tromey
2009-04-18 11:05       ` Eli Zaretskii
2009-04-18 17:34         ` Tom Tromey
2009-04-18 20:56           ` 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=m34owphjzm.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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