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 8CADE1F803 for ; Fri, 4 Jan 2019 21:25:29 +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:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=oIqGXtR1FGDm153X hG13OG9BaISzdHB99p/0cyKOd4/OFEMX7PKdakC276Uwr9VHGGgbzMxGguzvLHGx EIbj6BQlT3K/M4ZAncgkPf+dR7tZrrMwxVQwY+g2Ug2Ca25RCqIAznz8OYXc8U47 IBpYTakyEXLLooHdZ9ar+VPkAE4= 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:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=jrxFXO03jrssoQtxF/lj7K eYfoE=; b=kNNUASWtlb8a+7PsEJLBYjiA/MLve8VRZXXrWiYWyuliaFJGqlWs9Z mwSD63tGORyX1ZOqckDYcydsa7MtSjlG7WKlDf6tgoNwAbz7JZzmSslTwtSZWsq6 Q49JBptK2rotG5Dkd2+EG0r6f8Y3UuK1bAcxaYz9oQzOUedm15ay4= Received: (qmail 23738 invoked by alias); 4 Jan 2019 21:25:27 -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 23719 invoked by uid 89); 4 Jan 2019 21:25:26 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-qt1-f175.google.com Subject: Re: glibc 2.29 - Winter is coming... To: Joseph Myers Cc: Rafal Luzynski , Siddhesh Poyarekar , GLIBC Devel 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> From: Carlos O'Donell Openpgp: preference=signencrypt Message-ID: <2385ce81-2711-957f-b3ad-530bb1e101df@redhat.com> Date: Fri, 4 Jan 2019 16:25:19 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 1/3/19 3:58 PM, Joseph Myers wrote: > 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?) Yes, it should include the character properties for U+32FF (if possible). Yes we care about compatibility decomposition when computing the transliterated version of the Era name (see localedata/unicode-gen/gen_translit_compat.py (compatibility_decompose)). I'm going to handle the Era name change myself when it arrives unless someome beats me to it, we need it in RHEL. I will limit the backport as much as I can to reduce risk. -- Cheers, Carlos.