Re: [Ietf-languages] Proto-languages

drude@xs4all.nl Sat, 02 December 2023 15:37 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 33A16C14CE25 for <ietf-languages@ietfa.amsl.com>; Sat, 2 Dec 2023 07:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.441
X-Spam-Level:
X-Spam-Status: No, score=-6.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) 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 HLqsNjahbu8n for <ietf-languages@ietfa.amsl.com>; Sat, 2 Dec 2023 07:37:47 -0800 (PST)
Received: from out.mail.icann.org (out.mail.icann.org [64.78.33.6]) (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 AC7DFC14CF1A for <ietf-languages@ietf.org>; Sat, 2 Dec 2023 07:37:47 -0800 (PST)
Received: from MBX112-E2-CO-1.pexch112.icann.org (10.226.41.200) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Sat, 2 Dec 2023 07:37:46 -0800
Received: from aesmt112-va-1-2.serverpod.net (10.216.74.35) by MBX112-E2-CO-1.pexch112.icann.org (10.226.41.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28 via Frontend Transport; Sat, 2 Dec 2023 07:37:46 -0800
Received: from aesc112-va-1-1.serverpod.net (aesc112-va-1-1.serverpod.net [10.216.76.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aesmt112-va-1.serverpod.net (Postfix) with ESMTPS id 0C95A60003 for <ietf-languages@ex.icann.org>; Sat, 2 Dec 2023 07:37:46 -0800 (PST)
Received: from exmx112-va-1-2.serverpod.net (exmx112-va-1-2.serverpod.net [10.216.72.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aesmt112-va-1.serverpod.net (Postfix) with ESMTPS id CFF0A60002 for <ietf-languages@ex.icann.org>; Sat, 2 Dec 2023 07:37:45 -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 east.smtp.mx.icann.org (Postfix) with ESMTPS id 3B3001C0002 for <ietf-languages@ex.icann.org>; Sat, 2 Dec 2023 07:37:45 -0800 (PST)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.169]) (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 05D3570000D2 for <ietf-languages@iana.org>; Sat, 2 Dec 2023 15:37:44 +0000 (UTC)
X-KPN-MessageId: ae7e2800-9128-11ee-a148-005056abad63
Received: from smtp.kpnmail.nl (unknown [10.31.155.38]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id ae7e2800-9128-11ee-a148-005056abad63; Sat, 02 Dec 2023 16:37:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=xs4all01; h=content-type:mime-version:message-id:date:subject:to:from; bh=aBMwWTJBBDOd4FYASIGy/2F/+ha+X399WX+qJWgF/Ik=; b=h63SFyRoVS9rHOpCBEoNKF99x1n3bxtR0870R77xiBlibnTOKyKL2aUIWJmHFMIGis8dmMDIAESQM eDq60GIKI+CAxdRtdWOnnHyppl2tI6q8BIMblaK10ddo5XA4gm9WxGt/9wDgyGzeQYOdrABDFXQkHP YFgHJ0dLNgBZ4pCGtVw7Ehp6qRyP8iVLdKFmMoKuCIqfwEq9fo09nIoNY3KUSP1TxRMePJQkpe2d8C ZN5x8dOYu6aerXvLU6G2+9mwntitY83wit7NBvh58OYtMKICDUwHZdUYIwSvAceZHRirrrwjegQEa7 UK8HumrdYy3zD2lxZ22l5aRrx8pIPHA==
X-KPN-MID: 33|HxUBxlxoCxrs1lqs0WDm2BtoazxowO6xVl0CgEw37uorGJd2FFqP/FxWaSpYuJP IeMjeI7RR3Hh1qJnH24JzwrB4moTsXfgI0AAOJ4eCQY8=
X-KPN-VerifiedSender: Yes
X-CMASSUN: 33|e/9qyegiA92Tl9bzOGQoGarLLpIRgVEcdhaTXOUpV5V9dQYZ2orQIh2gheR/FC5 ihnSnTqYAcyZjWGpqTkGcXQ==
X-Originating-IP: 191.243.103.230
Received: from LAPTOPSTGT0CJL (unknown [191.243.103.230]) by smtp.xs4all.nl (Halon) with ESMTPSA id ad1bb031-9128-11ee-b971-005056abf0db; Sat, 02 Dec 2023 16:37:22 +0100 (CET)
From: drude@xs4all.nl
To: 'Richard Wordingham' <richard.wordingham=40ntlworld.com@dmarc.ietf.org>, 'IETF Languages Discussion' <ietf-languages@iana.org>
References: <20231202120313.6cb2007a@JRWUBU2>
In-Reply-To: <20231202120313.6cb2007a@JRWUBU2>
Date: Sat, 02 Dec 2023 12:37:17 -0300
Message-ID: <003a01da2535$7103f4b0$530bde10$@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJHMXuVr7VErPPo+lwv4OWP0mI5Da+8ArWA
Content-Language: en-us
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.4 cv=C8b6dCD+ c=1 sm=1 tr=0 ts=656b4f49 a=Z2iVbzAMQWfC12katpY7Eg==:117 a=Z2iVbzAMQWfC12katpY7Eg==:17 a=Ub29AZxUZ-EA:10 a=kj9zAlcOel0A:10 a=e2cXIFwxEfEA:10 a=8pif782wAAAA:8 a=48vgC7mUAAAA:8 a=I0CVDw5ZAAAA:8 a=lVqtWZrvqidvlpUdKlcA:9 a=CjuIK1q_8ugA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=YdXdGVBxRxTCRzIkH2Jn: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: e7cd4113-949e-4e1b-bb51-a88bcdd98b47
Spam-Stopper-v2: Yes
X-Envelope-Mail-From: drude@xs4all.nl
X-Spam-Reasons: None
X-AES-Category: LEGIT
X-Spam-Category: None
X-AES-Analytics-Data: eyJ0aW1lc3RhbXAiOiAiMjAyMy0xMi0wMlQxNTozNzo0NS45NDRaIiwgIm1lc3NhZ2VUcmFja2luZyI6IHsiaGFuZGxpbmciOiBbIlRISVJEIFBBUlRZIEJZUEFTUyJdLCAidW5pZmllZENhdGVnb3J5IjogIlVOQ0FURUdPUklTRUQifSwgImVuZ2luZXMiOiB7fX0=
X-Auto-Response-Suppress: DR, OOF, AutoReply
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/4vJDRxymAp2vPRN1jMZgfKC77NU>
Subject: Re: [Ietf-languages] Proto-languages
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: Sat, 02 Dec 2023 15:37:53 -0000

Dear Richard,

Indeed, when revising ISO 639, we discussed a number of times the question
of reconstructed (proto-)languages.

They are somewhat similar to constructed languages (such as Esperanto), but
they are usually not supported by a user community and there will generally
be only a few exemplary short text samples for each.  
Worse, as the reconstructions for one supposed proto-language may diverge
considerably from one researcher/enthusiast to the next, these text samples,
even if supposedly having the same content, diverge considerably (see
https://en.wikipedia.org/wiki/Schleicher%27s_fable).  The same holds for
individual reconstructed forms. 

Therefore, it is highly unlikely that they ever will be widely used in a way
that would warrant an ISO 639 code, and therefore this is explicitly not
possible: "Specifically excluded from the ISO 639 language code are
reconstructed languages [...]" and: "A reconstructed language inferred from
historical-comparative analysis but not attested from historical sources is
not considered eligible for language coding [...].".  

I would not attempt to submit such requests for new ISO 639 entries.

Best, Sebastian

-----Original Message-----
From: Ietf-languages <ietf-languages-bounces@ietf.org> On Behalf Of Richard
Wordingham
Sent: Saturday, 2 December, 2023 09:03
To: IETF Languages Discussion <ietf-languages@iana.org>
Subject: [Ietf-languages] Proto-languages

Greetings,

Some while ago, we had a brief discussion of the English Wiktionary's
non-conformant usage of language tags.  I have since discovered that these
non-conformant tags were being included used as language tags in the HTML of
the web site!  However, sentiment amongst the editors has moved towards it
being a good idea to emit conformant language tags, to the extent that we
are talking about generating a table converting Wiktionary language tags to
BCP 47-conformant tags, not necessarily preserving Wiktionary distinctions.

There are roughly 624 non-compliant Wiktionary language tags, whereas there
are only about 520 private use language subtags available.  A programme to
eliminate the need for private-use subtags will result in a flow of
registration requests.

A lot of these non-compliant language tags are for proto-languages, and I
foresee major problems in registering.  ISO 639-3 prohibits reconstructed
proto-languages, and the number of documents produced in proto-languages is
quite low.  Is there any point in trying to register them with ISO 639? If
so, how do we do it?

Another possibility I see is to register a variant subtag 'proto'
prefixable by any language subtag denoting a language family (formally, we
might have to generalise to anything with the scope of 'collection') to
denote the proto-language of the family.  If ISO 639 automatically rejects
mere proto-languages, is this in principle acceptable?  We might have to
list individual prefixes for the variant subtag, as roa-proto would denote
some variant of Latin (cf. la-peano for Interlingua).

A third possibility is to go for BCP 47 5-8 character language subtags.
 Would formal ISO 639 rejections be required?

Richard.

_______________________________________________
Ietf-languages mailing list
Ietf-languages@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-languages