From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17088 invoked by alias); 10 Oct 2019 16:25:00 -0000 Mailing-List: contact libc-locales-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-locales-owner@sourceware.org Received: (qmail 17060 invoked by uid 89); 10 Oct 2019 16:25:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=transitions, H*f:sk:9c492c4, H*i:sk:9c492c4, Holcroft X-HELO: mx1.redhat.com From: Florian Weimer To: Jean-Baptiste Holcroft Cc: libc-alpha@sourceware.org, libc-locales@sourceware.org Subject: Re: Language code changes over time: zh_CN -> zh_Hans References: <9c492c49060a079cf36b28269ea2a981@holcroft.fr> Date: Thu, 10 Oct 2019 16:25:00 -0000 In-Reply-To: <9c492c49060a079cf36b28269ea2a981@holcroft.fr> (Jean-Baptiste Holcroft's message of "Thu, 10 Oct 2019 17:22:47 +0200") Message-ID: <87lftsmuug.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2019-q4/txt/msg00014.txt.bz2 * Jean-Baptiste Holcroft: > the Fedora community is migrating to the Weblate translation platform. > This translation platform uses zh_Hans, zh_Hant, zh_Hant_HK by > default, instead of zh_CN, zh_TW and zh_HK. Is zh_Hant_HK perhaps a typo? Written as-is, that's going to be problematic. We had some bugs specific to the eo locale because its name does not have an underscore in it. I'm not sure if the language tag syntax is actually compatible with our locale names. For example, we write sr-Latn-RS (mentioned in RFC 5646) as sr_RS@latin. We have an aliasing mechanism, so we don't need to store the locale data several times over, so that part shouldn't be a problem. > If I understand correctly, we need to make sure the language code > exists in glibc before deciding using the new code for Linux > applications. > > The issue is as follow: a translation platform can be used by many > projects, not all using glibc, like Websites or mobile application who > already are using the new code. > > The web tells that the codes zh_CN, zh_TW, zh_HK are old codes and > should be replaced by the new ones. > Multiple sources tends to confirm this (and show that other actors > already did the move), the most relevant ones are: > https://www.w3.org/TR/i18n-html-tech-lang/#h2_langvalues This says: | Where possible, use the codes zh-Hans and zh-Hant to refer to Simplified | and Traditional Chinese, respectively. more... And the =E2=80=9Cmore...=E2=80=9D link goes to: which is dead. This isn't very reassuring. > What is the support status of these new language codes in Glibc? > If not supported, can we imagine to have backward compatibility while > upstream projects migrate to the new language code? > I assume these are not the only language code renaming, what policy do > you suggest concerning these? We must have renamed language codes in the past, but I don't remember any examples. Mostly we hadn't 1:1 replacements, but transitions due to changing political circumstances. There were also some language codes which were completely wrong. Thanks, Florian