[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAw4D034NMhpKAPfEG5yBAxVKwPeUPqxkSufvtGubDaxZZ-H1g@mail.gmail.com>
Date: Sun, 20 Oct 2019 11:53:15 +0300
From: Eleftherios Kritikos <el01049@...il.com>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH] Update ctype data to Unicode 12.1.0
Is anything else we could do to get this merged?
Kind regards,
Lefteris
On Mon, Oct 14, 2019 at 4:57 PM Eleftherios Kritikos <el01049@...il.com>
wrote:
> Actually now that I read the ISO spec again, it seems to correspond to
> Unicode 11 :( so I think ISO/IEC 10646 has not catch up with Unicode 12
> yet. Not sure what we should do in this case.
>
> On Mon, Oct 14, 2019 at 2:51 PM Eleftherios Kritikos <el01049@...il.com>
> wrote:
>
>> From what I read from here:
>>
>>
>> https://stackoverflow.com/questions/12590255/what-does-stdc-iso-10646-exactly-mean
>>
>> and here:
>>
>> https://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
>>
>> it seems like the latest ISO/IEC 10646 standard that most closely match
>> Unicode 12.1.0 is ISO/IEC 10646:2017/Amd 2:2019 (fifth edition 2017,
>> amendment 2).
>>
>> From what I read in the document here:
>> https://standards.iso.org/ittf/PubliclyAvailableStandards/c073773_ISO_IEC_10646_2017_Amd_2_2019%20(E).zip
>>
>> on first page, this amendment was made on 2019-06. So I would guess that
>> the correct value should be:
>>
>> ```
>> #define __STDC_ISO_10646__ 201906L
>> ```
>>
>> All this with a grain of salt as this is the first time I am looking at
>> ISO/IEC 10646.
>>
>> Thanks for looking into this!
>>
>> Regards,
>> Lefteris
>>
>>
>>
>> On Mon, Oct 14, 2019 at 2:07 PM Rich Felker <dalias@...c.org> wrote:
>>
>>> On Sat, Oct 12, 2019 at 11:56:44PM +0100, Eleftherios Kritikos wrote:
>>> > Yes. I also created a merge request for musl-chartable-tools
>>> > https://github.com/richfelker/musl-chartable-tools/pull/2
>>>
>>> Thanks. stdc-predef.h also needs to be updated with a new value for
>>> __STD_ISO_10646__. Do you know the right yyyymm value it should have
>>> for this version of Unicode?
>>>
>>> Rich
>>>
>>>
>>> > On Sat, 12 Oct 2019, 11:40 pm Rich Felker, <dalias@...c.org> wrote:
>>> >
>>> > > On Sat, Oct 12, 2019 at 10:27:42PM +0100, u_quark wrote:
>>> > > > ---
>>> > > > src/ctype/alpha.h | 159
>>> +++++++++++++++++++++-------------------
>>> > > > src/ctype/nonspacing.h | 88 ++++++++++++-----------
>>> > > > src/ctype/punct.h | 160
>>> ++++++++++++++++++++++-------------------
>>> > > > src/ctype/wide.h | 26 +++----
>>> > > > 4 files changed, 232 insertions(+), 201 deletions(-)
>>> > >
>>> > > Is this done just by dropping the new Unicode files into
>>> > > musl-chartable-tools and running make?
>>> > >
>>> > > Rich
>>> > >
>>>
>>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
