I sent this to SG16 (after tweaking it a bit to downplay UTF-16 and UTF-32).
On Mon, Apr 22, 2019 at 1:19 PM Henri Sivonen wrote:
>
> (If you don't care about what I say about character encoding issues in
> the context of C++ standardization outside my Mozilla activities, you
> can save time by skipping the rest of this email.)
>
> On my own time outside my Mozilla activities, I was invited to read
> and comment on the C++ standardization papers under the purview of the
> Unicode Study Group (SG16) of the C++ committee.
>
> I've drafted a reply in which I opine that _new_ text processing
> features (other than character encoding conversion facilities) in the
> C++ standard library should only support UTF-8/16/32 and should not
> seek to support non-UTF execution encodings and that conversion
> facilities should have an API similar encoding_rs's API:
> https://hsivonen.fi/p/non-unicode-in-cpp.html
>
> Based on prior advice from Botond, I'm sending this heads-up here just
> in case: If you have a reason why it would be bad from the Mozilla
> perspective for me to send the above-linked document to SG16 even with
> the personal-capacity disclaimer, please let me know.
>
> (I expect this to be non-controversial from the Mozilla perspective,
> since we already treat the concept of C++ "execution encoding" as a
> C++ design bug that we route around.)
>
> --
> Henri Sivonen
> hsivo...@hsivonen.fi
> https://hsivonen.fi/
--
Henri Sivonen
hsivo...@hsivonen.fi
https://hsivonen.fi/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
