From: Bruno Haible <bruno@clisp.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v16] POSIX locale covers every byte [BZ# 29511]
Date: Wed, 12 Jul 2023 23:08:28 +0200 [thread overview]
Message-ID: <13125305.F0gNSz5aLb@nimes> (raw)
In-Reply-To: <6row5r5lyev35lddwxlukyopx5j5faxaqlw2audnolca55zrhc@fvrom2u2wmaj>
> > How about mapping the bytes 0x80..0xFF to U+DF80..U+DFFF, like musl libc
> > does?
> That's what I had done originally (and citing the same exact reasons!),
> but changed it in v10
> https://sourceware.org/pipermail/libc-alpha/2023-April/147652.html
> because Florian likes it better. He forwarded it to musl@
> https://www.openwall.com/lists/musl/2022/11/10/1
Thanks for explaining. Sorry for the noise; I had not followed this thread.
gnulib's unit tests will have to change a bit, to accommodate glibc's
new behaviour. But that's an acceptable minor inconvenience.
Bruno
next prev parent reply other threads:[~2023-07-12 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 19:44 Bruno Haible
2023-07-12 20:22 ` наб
2023-07-12 21:08 ` Bruno Haible [this message]
-- 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=13125305.F0gNSz5aLb@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).