From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21]) by sourceware.org (Postfix) with ESMTPS id 551063858402 for ; Sun, 10 Oct 2021 16:07:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 551063858402 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=deneb.enyo.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=deneb.enyo.de Received: from [172.17.203.2] (port=37079 helo=deneb.enyo.de) by albireo.enyo.de ([172.17.140.2]) with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1mZbML-0007IB-W2; Sun, 10 Oct 2021 16:07:33 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.94.2) (envelope-from ) id 1mZbML-00080c-Kd; Sun, 10 Oct 2021 18:07:33 +0200 From: Florian Weimer To: Alexander Bantyev 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 References: Date: Sun, 10 Oct 2021 18:07:33 +0200 In-Reply-To: (Alexander Bantyev's message of "Sun, 10 Oct 2021 18:53:00 +0300") Message-ID: <878rz0zwvu.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-6.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Oct 2021 16:07:37 -0000 * Alexander Bantyev: > The file localedef/locales/iso14651_t1_common is, as far as I can tell, > supposed to be taken from . > 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: > > > 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.