Re: [Ietf-languages] Fwd: I-D Action: draft-msporny-d-langtag-ext-00.txt

"Doug Ewell" <doug@ewellic.org> Tue, 28 May 2019 00:25 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 700991200E6 for <ietf-languages@ietfa.amsl.com>; Mon, 27 May 2019 17:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 5QkSudsWT27a for <ietf-languages@ietfa.amsl.com>; Mon, 27 May 2019 17:25:25 -0700 (PDT)
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 1FC07120099 for <ietf-languages@ietf.org>; Mon, 27 May 2019 17:25:25 -0700 (PDT)
Received: by mork.alvestrand.no (Postfix) id 6BA2F7C37FE; Tue, 28 May 2019 02:25:23 +0200 (CEST)
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 577AE7C37E9 for <ietf-languages@alvestrand.no>; Tue, 28 May 2019 02:25:23 +0200 (CEST)
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 BsnPWWHsdiJ4 for <ietf-languages@alvestrand.no>; Tue, 28 May 2019 02:25:21 +0200 (CEST)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.33.72; helo=pechora2.lax.icann.org; envelope-from=doug@ewellic.org; receiver=ietf-languages@alvestrand.no
Received: from pechora2.lax.icann.org (pechora2.icann.org [192.0.33.72]) by mork.alvestrand.no (Postfix) with ESMTPS id 0D4F77C37CE for <ietf-languages@alvestrand.no>; Tue, 28 May 2019 02:25:20 +0200 (CEST)
Received: from p3plsmtpa11-09.prod.phx3.secureserver.net (p3plsmtpa11-09.prod.phx3.secureserver.net [68.178.252.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora2.lax.icann.org (Postfix) with ESMTPS id 4929E1E0119 for <ietf-languages@iana.org>; Tue, 28 May 2019 00:25:17 +0000 (UTC)
Received: from DESKTOPLPOB1E4 ([73.229.14.229]) by :SMTPAUTH: with ESMTPSA id VPvDhBROQmycsVPvEhWgWQ; Mon, 27 May 2019 17:24:57 -0700
From: Doug Ewell <doug@ewellic.org>
To: 'Richard Wordingham' <richard.wordingham=40ntlworld.com@dmarc.ietf.org>
Cc: 'IETF Languages Discussion' <ietf-languages@iana.org>, 'Mark Davis ☕️' <mark@macchiato.com>, "'Martin J. Dürst'" <duerst@it.aoyama.ac.jp>, 'Manu Sporny' <msporny@digitalbazaar.com>, "'Phillips, Addison'" <addison@lab126.com>
References: <155881874982.30992.4869767614014356043@ietfa.amsl.com> <49b6a1de-e016-514f-90e4-24703b5818d2@it.aoyama.ac.jp> <63b4f786-8b44-ecdf-ed33-ff0567ecc839@digitalbazaar.com> <000001d51425$a48ac140$eda043c0$@ewellic.org> <CAJ2xs_EwKg3Tu5etk-ELXXd0u2Go-6TZbGm3QsBxV1upKTa8_g@mail.gmail.com> <000001d514ae$b15bdbf0$141393d0$@ewellic.org> <CAJ2xs_GiwkqHPxsoW91ZbA82o1oosXNb=Hm2XOuKuEkMMcNBhA@mail.gmail.com> <000d01d514ce$98e0de70$caa29b50$@ewellic.org> <20190527233445.466d1a54@JRWUBU2>
In-Reply-To: <20190527233445.466d1a54@JRWUBU2>
Date: Mon, 27 May 2019 18:24:56 -0600
Message-ID: <000201d514eb$c7868690$569393b0$@ewellic.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQKLCtGP2z0dTCPwWpJCCMnlEYhybwL64n7IAmGOKmIBrGprnQHBCMpOAbXN25wCHv9nrAIONTERAZUV/fukka8sAA==
X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.6.2 (pechora2.lax.icann.org [192.0.33.72]); Tue, 28 May 2019 00:25:17 +0000 (UTC)
X-CMAE-Envelope: MS4wfBZ82fhhQ1OlZ/sE1auab+MeS5yKmI5GFvIO6g9xbCaz4he0hUGaHfFiV2yYCUO0/WCpL+61WUE8Or8uE7biBw5eKv1IgpcbcRR6HiVkn99wM6zhMAA4 snB31t+05K+d1QbWUHibpGwO2GqHxsffnjQL+HQcAffzersP0b3P2ek2bnguAgdF4fbig3YZHABxrZ0WzTe8xfZcRPpu9aesMUIgcIoGTLRtHdStFys+4BrJ sY6hd/smaSxu+EtPMYLZjreWdLdWoyUZ0ix2sgHhS6k6UyMn8RM08+Kf2MCoTmC6xRaH/Q1rA0UJd5OxUaqa2+sYCmj+RsIibknSMVYWFCgxlwriD7DTpAXY 7hog18vxWRQMWiLAEvjp/VsHMT7jew==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/oPUJJyxnTBSbMZ9rlHKr-aEcUNY>
Subject: Re: [Ietf-languages] Fwd: I-D Action: draft-msporny-d-langtag-ext-00.txt
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: Tue, 28 May 2019 00:25:26 -0000

Richard Wordingham wrote:

> So how do you use a present-day language tag to set the paragraph
> direction for Middle Egyptian in hieroglyphs?  Do you have to do
> something like ensuring that the scope of the Middle Egyptian language
> tag doesn't extend to the starts of paragraphs?  (Reminder: Ancient
> Egyptian Egyptian hieroglyphs could be laid out in either order;
> right-to-left was the default, but nowadays the default is left to
> right, apparently even in Arabic publications!

Mark suggested that even the present-day Chinese, Japanese, Korean, and Mongolian use cases were somewhat out of scope, so I suspect Middle Egyptian might also be beyond the use case that is being discussed here.

The quick answer is that BCP 47 language tags do not cover that. That is what the D extension proposal aims to solve.

My arguments regarding the proposed D extension have been that:

(a) for the posited use cases, primarily Arabic, the proposed solution is not necessary, because explicit or implicit script subtags already indicate direction, and

(b) for use cases such as mine, the proposed solution is not sufficient, because the repertoire is not extensible.

> And what if you want to have English text in right-to-left paragraphs?

I assumed we were sticking to real-life use cases. That said, in BabelPad I get the desired result with a Latin-script line by prefixing it with RLO.

--
Doug Ewell | Thornton, CO, US | ewellic.org