From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 9D24E1F803 for ; Mon, 7 Jan 2019 18:59:37 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=xp8YM JRGKl+Nb9YOqNeQjtUT0oIrG3iEc+kDpAuSKD4D0P89Pd/VXI0wYPwKUksDXUbV/ Lw1hsldkPfiXvkQrD7L0shkNN2vD7gMgheSeNI0vXcgo+RVo+rTK5FGscmQTy9ZZ HThHlnfArupJrHXJCqy3dyiHavcX4AJyJezCYs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=rzEyIlGg+V9 Ax7PSAgEpch9TbH0=; b=rb2/osW87jUARlV2x5BlZjbjRVl73VjUKYxLcllze36 Qyv3540LU9b0GzvZIxMAcNrTzpujF4PkNRj5GVr0/Iqotcp2S7VVWXz6ipjH8hO7 tYfck36jpb4GuH+rrWUJz+MZ0gb/C6sn8qQjtN9R6Th++WQPMiHpOepxApGUpbFg = Received: (qmail 69043 invoked by alias); 7 Jan 2019 18:59:35 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 69027 invoked by uid 89); 7 Jan 2019 18:59:34 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mx1.redhat.com From: Florian Weimer To: Joseph Myers Cc: Carlos O'Donell , Rafal Luzynski , Siddhesh Poyarekar , GLIBC Devel Subject: Re: glibc 2.29 - Winter is coming... References: <833db514-f25e-0c41-bf06-b8cc9272f1c2@gotplt.org> <87r2dv495n.fsf@oldenburg2.str.redhat.com> <1188732039.598484.1546429949188@poczta.nazwa.pl> <0c9a2e87-8b43-725a-d9cc-689ec032ba96@gotplt.org> <2063591203.633198.1546474845289@poczta.nazwa.pl> <75bc5d8f-d568-d5e1-aacf-fa19beaac81b@redhat.com> Date: Mon, 07 Jan 2019 19:59:24 +0100 In-Reply-To: (Joseph Myers's message of "Thu, 3 Jan 2019 20:58:24 +0000") Message-ID: <87zhsce1kj.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain * Joseph Myers: > On Thu, 3 Jan 2019, Carlos O'Donell wrote: > >> The new Era name will likely have to be backported to all the active >> open stable branches so they can display the new Era name. > > Presumably that includes the character properties for U+32FF? (Does > anything in glibc care about the to-be-announced compatibility > decomposition that's the reason Unicode 12.1 will be needed > or is glibc only > concerned with character properties that are already known?) It seems that the CLDR data has a transliteration for the other era characters. I don't know how relevant this to glibc. I'm pretty sure we need to adjust the collation data for U+32FF. For the era data itself, we also need to know the multi-character era name, so knowing the U+32FF codepoint is of little help (in the sense that we can ship the changes today and have other projects to supply the actual glyph shape). Thanks, Florian