Re: [Ietf-languages] Are BCP 47 collective language codes more suitable for zonal auxiliary languages than the "art" (Artificial) code?

Doug Ewell <doug@ewellic.org> Mon, 29 November 2021 05:05 UTC

Return-Path: <doug@ewellic.org>
X-Original-To: ietf-languages@ietfa.amsl.com
Delivered-To: ietf-languages@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3D93A0CAB for <ietf-languages@ietfa.amsl.com>; Sun, 28 Nov 2021 21:05:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6noVUSlYN6F7 for <ietf-languages@ietfa.amsl.com>; Sun, 28 Nov 2021 21:05:49 -0800 (PST)
Received: from p3plsmtpa12-05.prod.phx3.secureserver.net (p3plsmtpa12-05.prod.phx3.secureserver.net [68.178.252.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA863A0CAE for <ietf-languages@ietf.org>; Sun, 28 Nov 2021 21:05:49 -0800 (PST)
Received: from DESKTOPLPOB1E4 ([71.237.1.75]) by :SMTPAUTH: with ESMTPSA id rYrLmu6N4QJHprYrMmOCfj; Sun, 28 Nov 2021 22:05:48 -0700
X-CMAE-Analysis: v=2.4 cv=RK52o6u+ c=1 sm=1 tr=0 ts=61a45fac a=6nY1uNNCgC/8Ccg2lpAcFA==:117 a=6nY1uNNCgC/8Ccg2lpAcFA==:17 a=IkcTkHD0fZMA:10 a=te1EGT4yAAAA:8 a=nORFd0-XAAAA:8 a=C_6y8nXt3TR86OMQLygA:9 a=QEXdDO2ut3YA:10 a=RRElR4r2U1jGY2dU47NL:22 a=AYkXoqVYie-NGRFAsbO8:22
X-SECURESERVER-ACCT: doug@ewellic.org
From: Doug Ewell <doug@ewellic.org>
To: 'Yaroslav Serhieiev' <noomorph@gmail.com>, ietf-languages@ietf.org
References: <CALTz4dJ-n6-Mx6_1zGDkQ4dCLr1iMWzywunYk_xhAZfwEHCxMQ@mail.gmail.com>
In-Reply-To: <CALTz4dJ-n6-Mx6_1zGDkQ4dCLr1iMWzywunYk_xhAZfwEHCxMQ@mail.gmail.com>
Date: Sun, 28 Nov 2021 22:05:47 -0700
Message-ID: <000001d7e4de$c654ae30$52fe0a90$@ewellic.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH1NCdGbdlOBBAy5x2LiryJhT6BFqvfUiQg
Content-Language: en-us
X-CMAE-Envelope: MS4xfAU70lPmyjebdy8FbhscvK1Ixtt3h1JulkwwS4VqX3qm3ZHeAv7r3kIQ1gFN6c11Fyi8vfUPAKRj1w6M1ryL3RYRa+gRY0bBrlEL7zbi/9NWTYQBgcY4 Ub++gPKkvUCvcZd5TJVJMbCXhoFkcYUS2U1PFgyujp/SwbM6RoR1bWp+OJGkd+EuvZGcsQ8ELx5AIfJofOLPx54ft6nbXkpF2iY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/vTtVSBcdsYjdd7DXMNfEZMsMil0>
Subject: Re: [Ietf-languages] Are BCP 47 collective language codes more suitable for zonal auxiliary languages than the "art" (Artificial) code?
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Review of requests for language tag registration according to BCP 47 \(RFC 4646\)" <ietf-languages.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-languages/>
List-Post: <mailto:ietf-languages@ietf.org>
List-Help: <mailto:ietf-languages-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Nov 2021 05:05:55 -0000

Yaroslav Serhieiev wrote:

> P. S.  On the more practical side (here I attached a screenshot from
> LibreOffice with Hunspell dictionaries for Interslavic language), the
> software support is close to zero in both cases, be it art-... or
> sla-..., giving a second-class citizen experience for anyone who tries
> to strictly follow the recommendations. After a discussion with LO
> developers in their Bugzilla tracker, we checked that none of the
> potentially correct codes (art, sla) is present in the Unicode CLDR
> registry, which makes me wonder if they ever will be added there?

I'm not sure how CLDR would go about adding locale information for any of the "collection" language tags, for the simple reason that these tags represent multiple languages. Any locale information that would be correct for one member of the collection would not necessarily be correct, and might be profoundly wrong, for other members.

There is a separate CLDR mailing list; details are at https://corp.unicode.org/mailman/listinfo/cldr-users . (Sorry to keep redirecting you to different mailing lists, but this group does not control what goes into CLDR, although some of the main players happen to be here.)

--
Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org