From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14840 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eleftherios Kritikos Newsgroups: gmane.linux.lib.musl.general Subject: Re: [PATCH] Update ctype data to Unicode 12.1.0 Date: Sun, 20 Oct 2019 18:26:42 +0300 Message-ID: References: <20191012212742.29880-1-el01049@gmail.com> <20191012223947.GH16318@brightrain.aerifal.cx> <20191014130709.GL16318@brightrain.aerifal.cx> <20191020145915.GD16318@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000067af8c0595593252" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="130279"; mail-complaints-to="usenet@blaine.gmane.org" To: musl@lists.openwall.com Original-X-From: musl-return-14856-gllmg-musl=m.gmane.org@lists.openwall.com Sun Oct 20 17:27:08 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1iMD6q-000XpL-9r for gllmg-musl@m.gmane.org; Sun, 20 Oct 2019 17:27:08 +0200 Original-Received: (qmail 1940 invoked by uid 550); 20 Oct 2019 15:27:05 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 1922 invoked from network); 20 Oct 2019 15:27:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=hFc0Myk8dvydP1P1/Gd9Gm+w1LZcsEpogD8ftQZlRK4=; b=duszN4+9TvCgMgU6wzjs+IIWmuDjImPgjLO6BoeFAO0q30nl4rDqbDx+B4zdS5AcY1 5St2geW7gJORMuTjl4vjnZetEeLcqP4K2w3VIwMmJ2rPwlB1ycFr9LXJeRXORjt9qprK dd6hKUawkTQ65t91oMfP2y2im6bNBRe2fwxZKPk9lPQ/7bYNb4RgXFLA3mvtzhneqJHm i99fGR8KzTWrNsJEfkXJhdtxqJod4aWvvIN0KD5PB9zLhzVaiqICFoIlYObR6FbjUAvs 1y+HP9Dhei8w9sq6FKcSWHH0C7YZulCGfgL9GcBD1xizw1+8SyLMwNzmO3rhTQ1YpEFQ GkgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=hFc0Myk8dvydP1P1/Gd9Gm+w1LZcsEpogD8ftQZlRK4=; b=rvZ6pD3iMv7Iv15ekDVeiIqfpbR8pmTmOczh3gTiYxCKp+H1SLqgaR+5O1vRPm+vdg jaVsY6SzOeVgRbhWMTMEISIpJ09m5loQA0ux+Qr9fF+cqGhDC0btlkD3qySY+/w3e5TO 05AhGQaiLIGkkuSSeScN5bULwg0hjzmgAWxuuMVbQR+FrdFjLZhhVXxh4tZPgZcaBvqx jLAuwv9SrQDeMHbE1fn4GwIgYj35rTA95SO7iI+gplFHrJSo8MPa5u+J1VC6ht5Px2/r fDepbO4aWi91warqbyyXECYl0aJa8Wxnav6kAdO2hKH6tWAqbhVbHjFjxxFZrE7Ia/+U 8LVA== X-Gm-Message-State: APjAAAW1b4/CKc2Qt0YwOTxUSVwkngk6PDPq6UeOdd44kybDl6DGONb7 4ElZB0GPNmHC+Inyn3oOVo/kc5X2861layXCkGDlJeCBdE4= X-Google-Smtp-Source: APXvYqzvyj9KXOTuG5ddyQb/FoVNg3SpIFoA00zBOjgXaVaVN4B5PkGLBigWCKxklHfIZ/1nmya4ysyMd/5KHCx31Co= X-Received: by 2002:a19:ac01:: with SMTP id g1mr11903629lfc.141.1571585213835; Sun, 20 Oct 2019 08:26:53 -0700 (PDT) In-Reply-To: <20191020145915.GD16318@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:14840 Archived-At: --00000000000067af8c0595593252 Content-Type: text/plain; charset="UTF-8" Thanks a lot for looking into this. On Sun, Oct 20, 2019 at 5:59 PM Rich Felker wrote: > Thanks for pinging. I think we just need to go with the previous > __STDC_ISO_10646__ macro value for now until there's a new one. I > don't think it's a conformance problem to support additional new > characters we don't advertise support for with the macro, so it's not > a big deal. I can add it as a separate commit and update later with > another once there's a new value to be used. > I also think the value of the macro does not matter much. > BTW are there any new case mappings needed too? I can handle those if > so. (The current case mapping code needs manual work to update; I have > a draft replacement that won't need manual work I should really get > around to integrating.) > There might be! I haven't looked into that. Kind regards Lefteris --00000000000067af8c0595593252 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks a lot for looking into this.

On Sun, Oct 20, 20= 19 at 5:59 PM Rich Felker <dalias@lib= c.org> wrote:
Thanks for pinging. I think we just need to go with the previous
__STDC_ISO_10646__ macro value for now until there's a new one. I
don't think it's a conformance problem to support additional new characters we don't advertise support for with the macro, so it's n= ot
a big deal. I can add it as a separate commit and update later with
another once there's a new value to be used.

I also think the value of the macro does n= ot matter much.
=C2=A0
BTW are there any new case mappings needed too? I can handle those if
so. (The current case mapping code needs manual work to update; I have
a draft replacement that won't need manual work I should really get
around to integrating.)

There might be! I haven't looked into = that.

Kind regards
Lefteris

--00000000000067af8c0595593252--