While advancements in Unicode is a step, until we have a proper framework to enable users to support their own encodings cheaply and the ability to expand, I'm afraid that real progress will never be made.

I think we need to change some minds regarding the preferential treatment of Unicode instead of making everything else a second class citizens.

Not that the language needs to support everything, or that it should provide Unicode support. But because

I believe that the solutions required to get a levelled playing field are the same that will allow to properly deal with the problem of encoding zoos and locale independence.

I wish I had more time to work on this, but I got to eat.

From: SG16 <sg16-bounces@lists.isocpp.org> on behalf of Alisdair Meredith via SG16 <sg16@lists.isocpp.org>
Sent: Thursday, May 1, 2025 5:21:59 PM
To: Tom Honermann <tom@honermann.net>
Cc: Alisdair Meredith <alisdairm@me.com>; SG16 (WG21 Unicode) <sg16@lists.isocpp.org>; Peter Bindels <dascandy@gmail.com>; Hana Dusíková <hanicka@hanicka.net>; Jeremy Rifkin <jeremy@rifkin.dev>
Subject: [isocpp-sg16] Unicode an conversion facets

Thanks Tom.

I will admit to mild confusion on the rationale for keeping the code conversion facets,

unless we also want to withdraw support for adopting https://wg21.link/P2783 for C++26

as well?

Could I request guidance on what a replacement facility would look like, given the

current facility is built to support a framework based on runtime locales?

I understand that we do not want to remove something without a replacement, but

we will need a whole new text framework where character encoding is independent

of locale that do not have today. Mixing Unicode with runtime locales is a recipe for

text corruption, with no viable error handling in our current framework.

AlisdairM

On Apr 23, 2025, at 11:22 PM, Tom Honermann <tom@honermann.net> wrote:

Thank you to everyone that attended today.

WG21 members can find the draft meeting summary with poll results at https://wiki.edg.com/bin/view/Wg21telecons2025/SG16Teleconference2025-04-23.

Tom.