From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64269 invoked by alias); 12 Oct 2019 13:52:14 -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 64254 invoked by uid 89); 12 Oct 2019 13:52:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_50,BODY_8BITS,GARBLED_BODY,SPF_HELO_PASS autolearn=no version=3.3.1 spammy=JeanBaptiste, jean-baptiste, Jean-Baptiste, jeanbaptiste X-HELO: mx1.redhat.com From: Mike FABIAN To: Jean-Baptiste Cc: libc-locales@sourceware.org, libc-alpha@sourceware.org Subject: Re: Language code changes over time: zh_CN -> zh_Hans References: <9c492c49060a079cf36b28269ea2a981@holcroft.fr> Date: Sat, 12 Oct 2019 13:52:00 -0000 In-Reply-To: (jean-baptiste@holcroft.fr's message of "Sat, 12 Oct 2019 08:55:34 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2019-q4/txt/msg00019.txt.bz2 Jean-Baptiste さんはかきました: > Thank for your answers, I don't debate Weblate can use the old code. > > I see two issues: > 1. depending on the target platform, upstream project have to manually > convert language code used by the system > 2. The default setting in a translation platform is for every project, > it force every user project we host to remain on the old code by > default > > Short term solution is use old codes and I could have done it without telling anyone. > > But I feel like we need to have upstream support for new languages > code so we follow the standards evolution over time. Android did the > change years ago, Django also, Microsoft. Net also, and I'm sure we > can find other example. > > I'm confused on the reason why we have zh_Hans_CN in Locales folder, > does it means we can use it already? No, because gettext would find translations in that folder only if you set LC_MESSAGES=zh_Hans_CN.UTF-8, which you cannot: $ LC_ALL=zh_Hans_CN.UTF-8 locale charmap locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968 Maybe you can set LANGUAGE=zh_Hans_CN to make gettext find translations in that folder. We have several folders in /usr/share/locale/, some of them probably only because somebody made a mistake. For example: $ ls /usr/share/locale/zh_* -d /usr/share/locale/zh_CN/ /usr/share/locale/zh_Hant/ /usr/share/locale/zh_TW/ /usr/share/locale/zh_CN.GB2312/ /usr/share/locale/zh_Hant_TW/ /usr/share/locale/zh_TW.Big5/ /usr/share/locale/zh_Hans_CN/ /usr/share/locale/zh_HK/ zh_CN.GB2312 and zh_TW.Big5 make no sense. Or for Serbian: $ ls /usr/share/locale/sr* -d /usr/share/locale/sr/ '/usr/share/locale/sr@Latn'/ /usr/share/locale/sr_Cyrl/ /usr/share/locale/sr_ME/ /usr/share/locale/srd/ /usr/share/locale/srn/ '/usr/share/locale/sr@ije'/ /usr/share/locale/srr/ '/usr/share/locale/sr@ijekavian'/ /usr/share/locale/sr_RS/ '/usr/share/locale/sr@ijekavianlatin'/ '/usr/share/locale/sr_RS@latin'/ '/usr/share/locale/sr@latin'/ Why do we have sr@Latn and sr_RS@latin?? -- Mike FABIAN 睡眠不足はいい仕事の敵だ。