Re: [Ietf-languages] Latin Sub tags

Sebastian Drude <drude@xs4all.nl> Mon, 04 December 2023 21:42 UTC

Return-Path: <drude@xs4all.nl>
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 5912CC14CE4A for <ietf-languages@ietfa.amsl.com>; Mon, 4 Dec 2023 13:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.04
X-Spam-Level:
X-Spam-Status: No, score=-6.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=xs4all.nl
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1gwp81di0OK for <ietf-languages@ietfa.amsl.com>; Mon, 4 Dec 2023 13:42:53 -0800 (PST)
Received: from out.mail.icann.org (out.mail.icann.org [64.78.33.7]) (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 41100C14F6AF for <ietf-languages@ietf.org>; Mon, 4 Dec 2023 13:42:51 -0800 (PST)
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-E2-CO-1.pexch112.icann.org (10.226.41.200) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Mon, 4 Dec 2023 13:42:50 -0800
Received: from aesmt112-co-1-1.serverpod.net (10.224.74.75) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.129) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28 via Frontend Transport; Mon, 4 Dec 2023 13:42:50 -0800
Received: from aesc112-co-1-1.serverpod.net (aesc112-co-1-1.serverpod.net [10.224.76.90]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by aesmt112-co-1.serverpod.net (Postfix) with ESMTPS id 3EF0C40002 for <ietf-languages@ex.icann.org>; Mon, 4 Dec 2023 13:42:50 -0800 (PST)
Received: from exmx112-co-1-1.serverpod.net (exmx112-co-1-1.serverpod.net [10.224.72.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by aesmt112-co-1.serverpod.net (Postfix) with ESMTPS id 19A23120002 for <ietf-languages@ex.icann.org>; Mon, 4 Dec 2023 13:42:50 -0800 (PST)
Received: from pechora3.dc.icann.org (pechora3.icann.org [192.0.46.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by west.smtp.mx.icann.org (Postfix) with ESMTPS id 17EED180002 for <ietf-languages@ex.icann.org>; Mon, 4 Dec 2023 13:42:47 -0800 (PST)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pechora3.dc.icann.org (Postfix) with ESMTPS id EEA6D7000605 for <ietf-languages@iana.org>; Mon, 4 Dec 2023 21:42:46 +0000 (UTC)
X-KPN-MessageId: fe67785d-92ed-11ee-8346-005056ab378f
Received: from smtp.kpnmail.nl (unknown [10.31.155.38]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id fe67785d-92ed-11ee-8346-005056ab378f; Mon, 04 Dec 2023 22:42:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=xs4all01; h=from:to:subject:mime-version:date:message-id:content-type; bh=RFO5zsjNDcuB2JrxSrjE4Sywf+Hze0YPNWhWRnal+Ig=; b=X7wtsTlj9tC97LZiTtGaiogfMleolhMBXM/TY5r+lDykcMt2goUvWuIY1DntZQzI733K8kWDs/3LM snQsXStcyjwu/qWDyFYEgiUmjT/R6EKJUv0LFHCQPtNbWsoX62zpmlu6I6fol5cCLjSV2MOoQiI2Ad R9H1oh49eeNrNM2VzdsEV4mz5LWz+mD8ik6S0xf10OewBKtf4XWwAHkS/hOcAPr7/6s5x559HM2xUS psSJwMR1nxFkP/nqQiDBY+j0aFbVUBzSzoEgY0s6ofJpsV3BZz7/aZfA34jYL5Gq4RudRzVgP52iY5 Q6aQIYVSO2hMEj+YOvrCH38jPc6V0gA==
X-KPN-MID: 33|4ScMnaT3zwdCYGwnNrAgk6bQ85vtKvfOt+ra+v/pfzMYZA1GZ6dxqSY4xyV6lQD bocUyepvSUMM9bowidjADHRQs36pD+sQWLemOANA17ps=
X-KPN-VerifiedSender: Yes
X-CMASSUN: 33|aPyp86Tz0y9nZAPNY/ewlwj7rjA7crmzHM1zVlC9Z2QLxbWnHqzj4QSQrYPy27A 0qBmDWFwjsUdAlq8PElA+oQ==
X-Originating-IP: 187.180.124.116
Received: from [192.168.0.15] (unknown [187.180.124.116]) by smtp.kpnmail.nl (Halon) with ESMTPSA id ffe31f3e-92ed-11ee-b971-005056abf0db; Mon, 04 Dec 2023 22:42:23 +0100 (CET)
Content-Type: multipart/alternative; boundary="------------5S7dFJ710h0ps5chEmrbm40q"
Message-ID: <38dab9dc-a2bd-4598-b980-53b77ed1fc05@xs4all.nl>
Date: Mon, 04 Dec 2023 18:42:18 -0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: pt-BR
To: Doug Ewell <doug@ewellic.org>, Mark Davis ☕ <mark@macchiato.com>
CC: Hugh Paterson III <sil.linguist@gmail.com>, IETF Languages Discussion <ietf-languages@iana.org>
References: <CAE=3Ky-swzNn1hXba=muJF_radLugdKxhJ=u-_DcLiysDbothw@mail.gmail.com> <SJ0PR03MB6598925FCBA24238F417BE25CA82A@SJ0PR03MB6598.namprd03.prod.outlook.com> <CAE=3Ky_g3Sd7eBNq7H7_5BvkP-2qCbyYzQdO_eCSDzc70kQbJQ@mail.gmail.com> <012401da23b4$a9a291a0$fce7b4e0$@xs4all.nl> <SJ0PR03MB6598D48CD059645543661CA4CA81A@SJ0PR03MB6598.namprd03.prod.outlook.com> <018b01da2497$5094ed90$f1bec8b0$@xs4all.nl> <SJ0PR03MB65988A4F7614E585DF2BA6CBCA81A@SJ0PR03MB6598.namprd03.prod.outlook.com> <CAE=3Ky-jSJPg4pdKFbeabzHjOHzppasFV88J_v22RxKhATzxHA@mail.gmail.com> <000801da24b1$176928f0$463b7ad0$@xs4all.nl> <CAJ2xs_FSBeryEr=zwj85Ac7_xqfwyE=_rKRd25+fCvCHjLY9Gg@mail.gmail.com> <SJ0PR03MB65986F9C11AEF8D81B038A81CA86A@SJ0PR03MB6598.namprd03.prod.outlook.com>
From: Sebastian Drude <drude@xs4all.nl>
In-Reply-To: <SJ0PR03MB65986F9C11AEF8D81B038A81CA86A@SJ0PR03MB6598.namprd03.prod.outlook.com>
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.4 cv=UvJwis8B c=1 sm=1 tr=0 ts=656e47d8 a=Z2iVbzAMQWfC12katpY7Eg==:117 a=Z2iVbzAMQWfC12katpY7Eg==:17 a=q9747OsrU8wA:10 a=e2cXIFwxEfEA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=xOd6jRPJAAAA:8 a=nORFd0-XAAAA:8 a=99fI5vRuelW3UnMauvQA:9 a=QEXdDO2ut3YA:10 a=UqCG9HQmAAAA:8 a=Mp2CG1kxF9JyfvloekUA:9 a=XJWgD0iJLTAlWY__:21 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10 a=AYkXoqVYie-NGRFAsbO8:22
X-SOURCE-IP: 192.0.46.73
X-SPF-STATUS: soft_fail
X-SPF-FROM-STATUS: not_checked
X-RDNS-STATUS: pass
X-HELO-STRING: pechora3.dc.icann.org
Spam-Stopper-Id: 130a769b-aa20-412d-9a83-86df07339991
Spam-Stopper-v2: Yes
X-Envelope-Mail-From: drude@xs4all.nl
X-Spam-Reasons: None
X-AES-Category: LEGIT
X-AES-Analytics-Data: eyJ0aW1lc3RhbXAiOiAiMjAyMy0xMi0wNFQyMTo0Mjo1MC4xNzVaIiwgIm1lc3NhZ2VUcmFja2luZyI6IHsiaGFuZGxpbmciOiBbIlRISVJEIFBBUlRZIEJZUEFTUyJdLCAidW5pZmllZENhdGVnb3J5IjogIlVOQ0FURUdPUklTRUQifSwgImVuZ2luZXMiOiB7fX0=
X-Spam-Category: None
X-Auto-Response-Suppress: DR, OOF, AutoReply
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/vQ9ASeAA2bk-Yp6uBQGsZZE-F34>
Subject: Re: [Ietf-languages] Latin Sub tags
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.39
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, 04 Dec 2023 21:42:59 -0000

I remember having read that the "macrolanguage"-scope was invented and 
applied merely in the context of harmonizing the Ethnologue database 
with the existing ISO-639-2 codeset when Part 3 was implemented.  So I 
would be surprised if many new code elements with that scope would have 
been created since then, and I believe that in the future such requests, 
while not excluded (see below), would need very good support, especially 
if they change the meaning of existing code elements and threaten to 
break existing applications, as Mark rightly pointed out.  And I also 
agree, the inconsistency (comparing, for instance, *ar* with *de*) that 
Mark points out is worrying, and I do not have any coherent and 
practicable solution.

Excerpt from the new ISO 639:

6.2.4    Eligibility of a macrolanguage for language coding

To qualify as a macrolanguage, a proposed macrolanguage code element 
shall meet the following criteria:

  * The encompassed individual languages shall be closely related.
  * Some applications require that a language be treated like an
    individual language in public data interchange.
  * Other applications require that the same language be subdivided into
    two or more individual languages in public data interchange.
  * The relationship between the macrolanguage code element and the
    encompassed individual-language code elements are explicitly
    defined, i.e. there is a defined mapping from the macrolanguage code
    element to two or more specific individual-language code elements.
  * A macrolanguage code element shall not encompass another
    macrolanguage or language group.
  * The creation of new macrolanguage code elements or the widening of
    an existing individual-language code element to the scope of a
    macrolanguage shall be based on evidence of application requirements
    for public data interchange, as well as appropriate linguistic
    relationships between the individual languages involved.

Sebastian

-- 
Museu P.E. Goeldi, CCH, Linguistica ▪ Av. Perimetral, 1901
Terra Firme, CEP: 66077-530 ▪ Belém do Pará – PA ▪ Brazil
drude@xs4all.nl  ▪ +55 (91) 3217 6024 ▪ +55 (91) 983733319
Priv: Tv. Juvenal Cordeiro, 184, Apt 104 ▪ 66070-300 Belém

On 04/12/2023 17:44, Doug Ewell wrote:
> Mark Davis wrote:
>
>> While it is too late to change the macrolanguage structure, I would
>> advise against further “reclassifications”, since they just make it
>> harder for people, not easier.
> Based on a search of the Summary of Outcomes documents, it appears that no individual languages have been reclassified as macrolanguages since 2012 (Nepali and Oriya, now Odia), and that no brand-new macrolanguage code elements have ever been created since the inception of the ISO 639-3 annual review cycles in 2006.
>
> All macrolanguage-related changes since then have been to members of a macrolanguage (i.e. encompassed languages): adding them, removing them, or reclassifying their Scope from Active to Retired.
>
> A better analysis would be to scan the 639-3 code set files programmatically, looking for changes in the Scope field of existing alpha-3 code elements from “I” to “M”.
>
> --
> Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org
>