public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John Scott <jscott@posteo.net>
To: libc-alpha@sourceware.org
Subject: Report: __STDC_ISO_10646__ constant is out-of-date
Date: Fri, 09 Oct 2020 23:02:00 -0400	[thread overview]
Message-ID: <2753065.4ZSdVeJahi@t450> (raw)

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

Hello,

I prefer to send my bug report here instead of registering on Bugzilla and 
hope that's alright. I'm also not subscribed; please keep me CC'd.

I'm using glibc 2.30 on Debian GNU/Linux. 2.30 and 2.32 appear to have added 
support for Unicode 12.1.0 and 13.0 respectively [1] [2], but stdc-
predef.h [3] even in git seems to lag behind reflecting these changes:
> /* wchar_t uses Unicode 10.0.0.  Version 10.0 of the Unicode Standard is
>    synchronized with ISO/IEC 10646:2017, fifth edition, plus
>    the following additions from Amendment 1 to the fifth edition:
>    - 56 emoji characters
>    - 285 hentaigana
>    - 3 additional Zanabazar Square characters */
> #define __STDC_ISO_10646__              201706L
so in this way clients won't be able to know that it's supported. Except for 
some possible discrepancy in Unicode Inc. and ISO/IEC's release dates, 
suitable constants for 2.32 and 2.30 ought to be 202003L and 201905L 
respectively [4].

Regards,
John

[1] https://sourceware.org/legacy-ml/libc-alpha/2019-08/msg00029.html
[2] https://sourceware.org/pipermail/libc-announce/2020/000029.html
[3] https://sourceware.org/git/?p=glibc.git;f=include/stdc-predef.h;hb=HEAD
[4] https://www.unicode.org/history/publicationdates.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2020-10-10  3:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10  3:02 John Scott [this message]
2020-10-10  3:17 ` Carlos O'Donell
2020-11-06  5:56   ` John Scott

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=2753065.4ZSdVeJahi@t450 \
    --to=jscott@posteo.net \
    --cc=libc-alpha@sourceware.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).