Re: [Ietf-languages] Moldovan

Sascha Brawer <sascha@brawer.ch> Mon, 11 February 2019 18:33 UTC

Return-Path: <sascha.brawer@gmail.com>
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 D7FDB131110 for <ietf-languages@ietfa.amsl.com>; Mon, 11 Feb 2019 10:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level:
X-Spam-Status: No, score=-1.213 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.018, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 Cdc8FAnVfM7O for <ietf-languages@ietfa.amsl.com>; Mon, 11 Feb 2019 10:33:30 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B717813110B for <ietf-languages@ietf.org>; Mon, 11 Feb 2019 10:33:29 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id D22F77C4040; Mon, 11 Feb 2019 19:33:27 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id C19327C3F98 for <ietf-languages@alvestrand.no>; Mon, 11 Feb 2019 19:33:27 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I637h6kuvjLw for <ietf-languages@alvestrand.no>; Mon, 11 Feb 2019 19:33:25 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.46.72; helo=pechora6.dc.icann.org; envelope-from=sascha.brawer@gmail.com; receiver=ietf-languages@alvestrand.no
Received: from pechora6.dc.icann.org (pechora6.icann.org [192.0.46.72]) by mork.alvestrand.no (Postfix) with ESMTPS id 80EBE7C3D7E for <ietf-languages@alvestrand.no>; Mon, 11 Feb 2019 19:33:25 +0100 (CET)
Received: from mail-it1-f174.google.com (mail-it1-f174.google.com [209.85.166.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pechora6.dc.icann.org (Postfix) with ESMTPS id 4FE0C1E0133 for <ietf-languages@iana.org>; Mon, 11 Feb 2019 18:33:23 +0000 (UTC)
Received: by mail-it1-f174.google.com with SMTP id i2so615386ite.5 for <ietf-languages@iana.org>; Mon, 11 Feb 2019 10:33:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nB9fmgpWkbz6zv2xgX9HOnDOwoD7Nybrifq7c0hXG2Y=; b=pEwNFbuLNrhnLzF3b2D44nVDa4FoBezlqqiZ/1a8Wfe8uSqrT4Yh7rj8OhhIqC0wV2 x5yz+LIBLKrmz5jDZlLNrqxm1qMURRLh5BCmSypJRUAoZatQIowEykL1yrj4fb13e5vf z7T2HKzMsWkyTr8ttq1vMs0z3RQiMQNUZpYs54SrAF/Ead1vrI/3J6Z9CRcF9DsKRqdv 8dwMsHnrAoV8d6wy3U615Q5kJLA27G8s6IIJ8v/umTpMDZd121AyLsO3Yb5jg6PI3lce Ili3DDK+CNloXpH/5QPyemEhY84wiATu+Zwy8BVGQpWICLQfT54uwBGpLtkDHRRm1EjK s91A==
X-Gm-Message-State: AHQUAuaoJIx3Tdrgnq7Jp5YyKtTBr/l1zV02Gf/05GwWjIIb2n78oL1X wgrOqrbWMf8g9Eb8cH3QcXyeym2LegXrefIOnFRxXier
X-Google-Smtp-Source: AHgI3IbIpyOaZckpSx8p9lxhOmpF3MM/K12gS15WnvBF53JRzwxLNVRq5U/W6Pdbfx2scZC5qHj2f/5QDCWuFnoD9i8=
X-Received: by 2002:a24:ee83:: with SMTP id b125mr515072iti.151.1549909983147; Mon, 11 Feb 2019 10:33:03 -0800 (PST)
MIME-Version: 1.0
References: <20190211104041.665a7a7059d7ee80bb4d670165c8327d.cf3c4de81e.wbe@email03.godaddy.com>
In-Reply-To: <20190211104041.665a7a7059d7ee80bb4d670165c8327d.cf3c4de81e.wbe@email03.godaddy.com>
From: Sascha Brawer <sascha@brawer.ch>
Date: Mon, 11 Feb 2019 19:32:52 +0100
Message-ID: <CABKQ4ET+++3XmGss=XKz81pmmoS2cZ2EWvZeJpcXnRdnBywXSg@mail.gmail.com>
To: Doug Ewell <doug@ewellic.org>
Cc: ietflang IETF Languages Discussion <ietf-languages@iana.org>
Content-Type: multipart/alternative; boundary="000000000000fabfb70581a289f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/jeT4eINnSJn53S8g3sv0q4OY50M>
Subject: Re: [Ietf-languages] Moldovan
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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, 11 Feb 2019 18:33:32 -0000

Thanks for the explanation! There seems to be a list of all entries here:
https://www.iana.org/assignments/lang-subtags-templates/lang-subtags-templates.xhtml

> I wonder sometimes what folks are looking
> for when they look up the registration form years after the change has
> been made. . I still shake my head over the cross-reference, in the
> Wikipedia article on the Romansh language, to the LSR registration form
> for 'rm' that simply added a Suppress-Script. What sort of
> citation-worthy authority on the language does that provide?

For Wikipedia, the point is being able to fact-check claims in articles.
For example, this footnote:
https://en.wikipedia.org/wiki/Sursilvan#cite_note-wikidata-5ed25969116c8c3d94b94a12bbe06f082a068bc3-v3-3
allows to verify that the claimed BCP47 language tag is indeed the one
being mentioned in the article’s infobox.

— Sascha

Am Mo., 11. Feb. 2019 um 18:41 Uhr schrieb Doug Ewell <doug@ewellic.org>:

> Sascha's response displayed the URL better than my original response.
> Apologies for the way my phone sometimes formats mail messages.
>
> To explain a bit, registration forms for the Language Subtag Registry
> are transactional; they represent a single action (add or modify) and
> are never "updated."
>
> For example, a subtag 'zzz' could be created, then have its Description
> changed, then be deprecated (this could happen e.g. with lesser-known
> languages added to 639-3). This would result in three separate
> registration forms. The first would be "regform-zzz"; the latter two
> would be "regform-zzz-yyyy-mm-dd" indicating the date of the request or
> approval. We've had more than 40 of these "dated" registrations already.
>
> Registrations that were part of the RFC 4645 or 5645 bulk additions do
> not have registration forms. I wonder sometimes what folks are looking
> for when they look up the registration form years after the change has
> been made. I still shake my head over the cross-reference, in the
> Wikipedia article on the Romansh language, to the LSR registration form
> for 'rm' that simply added a Suppress-Script. What sort of
> citation-worthy authority on the language does that provide?
>
> --
> Doug Ewell | Thornton, CO, US | ewellic.org
>
>
>
> -------- Original Message --------
> Subject: Re: [Ietf-languages] Moldovan
> From: Sascha Brawer <sascha@brawer.ch>
> Date: Mon, February 11, 2019 7:04 am
> To: Doug Ewell <doug@ewellic.org>
> Cc: ietflang IETF Languages Discussion <ietf-languages@iana.org>
>
> Ah, got it; thank you.
>
> Am Mo., 11. Feb. 2019 um 13:30 Uhr schrieb Doug Ewell
> <doug@ewellic..org>:
>
>
>
> https://www.iana.org/assignments/lang-subtags-templates/mo-20081125.txt
>
>