From: Eleftherios Kritikos <el01049@gmail.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [PATCH] Update ctype data to Unicode 12.1.0
Date: Sun, 20 Oct 2019 11:53:15 +0300 [thread overview]
Message-ID: <CAAw4D034NMhpKAPfEG5yBAxVKwPeUPqxkSufvtGubDaxZZ-H1g@mail.gmail.com> (raw)
In-Reply-To: <CAAw4D02nmS5p+Dy6pfcOytBozMEqKCv7hRnWM_9OD+xu038v5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]
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@gmail.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@gmail.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@libc.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@libc.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
>>> > >
>>>
>>
[-- Attachment #2: Type: text/html, Size: 4286 bytes --]
next prev parent reply other threads:[~2019-10-20 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 21:27 u_quark
2019-10-12 22:39 ` Rich Felker
2019-10-12 22:56 ` Eleftherios Kritikos
2019-10-14 13:07 ` Rich Felker
2019-10-14 13:51 ` Eleftherios Kritikos
2019-10-14 13:57 ` Eleftherios Kritikos
2019-10-20 8:53 ` Eleftherios Kritikos [this message]
2019-10-20 14:59 ` Rich Felker
2019-10-20 15:26 ` Eleftherios Kritikos
2019-10-23 16:21 ` Eleftherios Kritikos
2019-10-25 14:15 ` Rich Felker
2019-10-25 14:29 ` Eleftherios Kritikos
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=CAAw4D034NMhpKAPfEG5yBAxVKwPeUPqxkSufvtGubDaxZZ-H1g@mail.gmail.com \
--to=el01049@gmail.com \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).