From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add UTF16/UTF32 target charsets in phony_iconv
Date: Sun, 16 Oct 2022 09:24:31 +0300 [thread overview]
Message-ID: <837d105lr4.fsf@gnu.org> (raw)
In-Reply-To: <878rlgedug.fsf@tromey.com> (message from Tom Tromey on Sat, 15 Oct 2022 19:50:31 -0600)
> From: Tom Tromey <tom@tromey.com>
> Date: Sat, 15 Oct 2022 19:50:31 -0600
> Cc: Patrick Monnerat via Gdb-patches <gdb-patches@sourceware.org>
>
> However, I think there's a better way to fix all this. It's very simple
> and offhand I don't know why I didn't think of it before... the use of
> wchar_t depends on knowing the encoding of wchar_t -- and I think we do
> know this on mingw, as it's a form of UTF-16.
Beware: wchar_t on MS-Windows _is_ indeed UTF-16, but that means a
single wchar_t character can only represent characters within the BMP;
anything beyond the BMP will need a 'wchar_t *' string whose length is
at least 2. So if the code converts single characters, on Windows it
can only do that with BMP codepoints.
(Ignore me if what I say makes no sense or is not useful: I wasn't
tracking this discussion.)
next prev parent reply other threads:[~2022-10-16 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 14:00 Patrick Monnerat
2022-10-07 20:10 ` Tom Tromey
2022-10-08 0:12 ` Patrick Monnerat
2022-10-08 18:55 ` Tom Tromey
2022-10-09 0:47 ` Patrick Monnerat
2022-10-10 16:11 ` Tom Tromey
2022-10-16 1:50 ` Tom Tromey
2022-10-16 6:24 ` Eli Zaretskii [this message]
2022-10-17 23:10 ` Tom Tromey
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=837d105lr4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).