public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Alexander Bantyev <balsoft@balsoft.ru>
Cc: libc-help@sourceware.org, mfabian@redhat.com, carlos@redhat.com
Subject: Re: [idea] Update ISO 14651 file in locales to the latest standard version
Date: Sun, 10 Oct 2021 18:07:33 +0200	[thread overview]
Message-ID: <878rz0zwvu.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CSQR0R.EMQXVP5812PZ@balsoft.ru> (Alexander Bantyev's message of "Sun, 10 Oct 2021 18:53:00 +0300")

* Alexander Bantyev:

> The file localedef/locales/iso14651_t1_common is, as far as I can tell,
> supposed to be taken from <https://standards.iso.org/iso-iec/14651>. 
> However,
> the version in glibc repository is quite old (from 2016, I think) and is
> missing some new Unicode codepoints. There have been new editions to the
> standard, the newest being edition 6 from 2020:
> <https://standards.iso.org/iso-iec/14651/ed-6/en/ISO14651_2020_TABLE1_en.txt>
>
> Perhaps the file in the glibc repository can be updated to match the
> latest standard?

I think it's scary to update this file because it alters the result of
bracket patterns in regular expressions.  The file is no longer fully
automatically generated, I think.  Implementing rational ranges where
it counts in glibc would be one way forward here.

Cc:ing Mike and Carlos, who have more details.

  reply	other threads:[~2021-10-10 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 15:53 Alexander Bantyev
2021-10-10 16:07 ` Florian Weimer [this message]
2021-11-02 16:52   ` Carlos O'Donell

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=878rz0zwvu.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=balsoft@balsoft.ru \
    --cc=carlos@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=mfabian@redhat.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. 
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).