From: Florian Weimer <fweimer@redhat.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: libc-alpha@sourceware.org, Victor Stinner <vstinner@redhat.com>
Subject: Re: [PATCH v6 2/2] POSIX locale covers every byte [BZ# 29511]
Date: Fri, 02 Dec 2022 18:36:26 +0100 [thread overview]
Message-ID: <87mt85pv1h.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20221128162453.supbaps5ftl2mg3s@tarta.nabijaczleweli.xyz> (=?utf-8?B?ItC90LDQsSIncw==?= message of "Mon, 28 Nov 2022 17:24:53 +0100")
* наб:
> 18-day bump :)
>
> On Thu, Nov 10, 2022 at 09:10:57AM +0100, Florian Weimer wrote:
>> Raised on the musl list here:
>> Choice of wchar_t mapping for non-ASCII bytes in the POSIX locale
>> <https://www.openwall.com/lists/musl/2022/11/10/1>
>
> That thread seems to've been exhausted (at least I don't see anything
> fresh in the archive) ‒ should I just resend with the comments for v7
> applied, or do you have a mapping range you'd rather see given those
> givens?
I still can't make up my mind. I think the options are:
* Some sort of custom encoding (like you posted).
* Latin-1
* UTF-8 with surrogate escape encoding (and encouraging POSIX to change again)
What argues in favor of the last point is that many, many people are
using C.UTF-8 nowadays. And effectively disabling wide/multibyte
conversion until you call setlocale does not seem particularly useful.
I have a feeling of déjà vu regarding this—I think I have investigated
non-setlocale defaults for wide/multibyte conversion in the past, but
can't find the previous discussion.
Thanks,
Florian
next prev parent reply other threads:[~2022-12-02 17:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 18:19 [PATCH] " наб
2022-09-06 14:06 ` [PATCH v2] " наб
2022-09-06 14:19 ` [PATCH] " Florian Weimer
2022-09-06 18:06 ` наб
2022-09-06 18:10 ` [PATCH v3 1/2] iconvdata/tst-table-charmap.sh: remove handling of old, borrowed format наб
2022-09-14 2:39 ` [PATCH v4 " наб
2022-09-21 14:01 ` [PATCH v5 " наб
2022-11-02 17:17 ` [PATCH v6 " наб
2022-11-09 12:49 ` Florian Weimer
2022-11-02 17:17 ` [PATCH v6 2/2] POSIX locale covers every byte [BZ# 29511] наб
2022-11-09 14:20 ` Florian Weimer
2022-11-09 16:14 ` [PATCH v7] " наб
2022-11-10 9:52 ` Florian Weimer
2023-01-09 15:17 ` [PATCH v8] " наб
2023-02-07 14:16 ` [PATCH v9] " наб
2023-02-13 14:52 ` Florian Weimer
2023-04-26 18:54 ` наб
2023-04-26 21:27 ` Florian Weimer
2023-04-27 0:17 ` [PATCH v10] " наб
2023-04-28 15:43 ` [PATCH v11] " наб
2023-05-07 22:53 ` [PATCH v12] " наб
2023-05-29 13:54 ` [PATCH v13] " наб
2022-11-10 8:10 ` [PATCH v6 2/2] " Florian Weimer
2022-11-28 16:24 ` наб
2022-12-02 17:36 ` Florian Weimer [this message]
2022-12-02 18:42 ` наб
2022-09-21 14:01 ` [PATCH v5 " наб
2022-09-14 2:39 ` [PATCH v4 " наб
2022-09-06 18:11 ` [PATCH v3 " наб
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=87mt85pv1h.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=vstinner@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).