From: Bruno Haible <bruno@clisp.org>
To: "Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v16] POSIX locale covers every byte [BZ# 29511]
Date: Wed, 12 Jul 2023 21:44:26 +0200 [thread overview]
Message-ID: <4881032.NnENhoQgcM@nimes> (raw)
Thank you for working on this.
Regarding the mapping of the bytes 0x80..0xFF:
> By strategically picking c=<UDC00> we land at the same point of the
> Unicode Low Surrogate Area at DC00-DCFF, described as
> > Isolated surrogate code points have no interpretation;
> > consequently, no character code charts or names lists
> > are provided for this range.
> as the Python UTF-8 errors=surrogateescape encoding.
musl libc maps the bytes 0x80..0xFF to U+DF80..U+DFFF. [1][2]
I think it is more useful to avoid an inconsistency between glibc and
musl libc, than to be consistent with what a particular user-space
program (Python) does.
How about mapping the bytes 0x80..0xFF to U+DF80..U+DFFF, like musl libc
does?
Bruno
[1] https://git.musl-libc.org/cgit/musl/tree/src/multibyte/internal.h#n19
[2] https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=tests/test-btowc.c#l71
next reply other threads:[~2023-07-12 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 19:44 Bruno Haible [this message]
2023-07-12 20:22 ` наб
2023-07-12 21:08 ` Bruno Haible
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 21:49 Bruno Haible
2023-07-12 23:51 ` наб
2023-07-03 15:39 наб
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=4881032.NnENhoQgcM@nimes \
--to=bruno@clisp.org \
--cc=libc-alpha@sourceware.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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).