C++ Logo


Advanced search

Re: [SG16-Unicode] It???s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++

From: keld_at <keld_at_[hidden]>
Date: Sat, 27 Apr 2019 15:27:27 +0200
On Sat, Apr 27, 2019 at 01:15:00PM +0000, Lyberta wrote:
> > use the posix/c/sc2 model of abstract characters that has been the model in iso for many
> > years and is also the model in the internet. no big deal. unicode is just a number of
> > harsets , utf8, utf16 utf32 etc.
> >
> > keld
> >
> I've looked at POSIX and the only thing I could find is this:
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html#tag_06_01
> This means zero Unicode support.

posix advocates using utf-8 as the externel chaset and 32 bit 10646 as internal widechar encoding

> As for C, C only has char16_t, char32_t, minimalistic literal support...
> I'm not sure about standard library. That's about 2% of Unicode support.

also look at iso 14651, 14652

what is missing? i know: quite a lot, but please examplify

> I don't know what is sc2.

this is iso/iec jtc1/sc2 - character sets -
they make all iso character sets including 10646.


Received on 2019-04-27 15:27:27