From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25729 invoked by alias); 10 Oct 2019 15:22:52 -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 25711 invoked by uid 89); 10 Oct 2019 15:22:52 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=HTo:U*libc-locales, H*Ad:U*libc-locales, websites, bcp X-HELO: holcroft.fr DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=holcroft.fr; s=mail; t=1570720967; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=pfeip9W/uxr7J38KG4yKpAbjp7uywVpXbu63rTve0ro=; b=AYTOfLyQ1uL3KHiWLY/L3VwGxCTPctJoOvRk7IoH8nSLQdAol0jC23S6f4w/OB9us5CJZZ O5sd+ndYIPEl+KjnH55myvAzuS311UKQe5hzMZXcLsDcVjK1IZxMIQGxFMdkrLVNLht19e nJQ1DPZa0vkLNKtzuc41m1MuypOg7yw= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 10 Oct 2019 15:22:00 -0000 From: Jean-Baptiste Holcroft To: libc-alpha@sourceware.org, libc-locales@sourceware.org Subject: Language code changes over time: zh_CN -> zh_Hans Message-ID: <9c492c49060a079cf36b28269ea2a981@holcroft.fr> X-Sender: jean-baptiste@holcroft.fr X-SW-Source: 2019-q4/txt/msg00013.txt.bz2 Hi, 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. 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 http://www.rfc-editor.org/rfc/bcp/bcp47.txt And the replacement rule is also in the CLDR: https://github.com/unicode-org/cldr/blob/ed7854cb6209678739712854a2df1cac732be540/common/supplemental/supplementalMetadata.xml#L177 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? Please do not hesitate to tell where this discussion should happen as this is my first contact with your community. Thanks a lot for your help, Jean-Baptiste