Re: [I18nrp] Last Call: <draft-faltstrom-unicode11-05.txt> (IDNA2008 and Unicode 11.0.0) to Informational RFC

John C Klensin <john-ietf@jck.com> Fri, 07 December 2018 20:02 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 260A2130FC4 for <i18nrp@ietfa.amsl.com>; Fri, 7 Dec 2018 12:02:57 -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_DNSWL_NONE=-0.0001] 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 ZIX5FXTcv5Zv for <i18nrp@ietfa.amsl.com>; Fri, 7 Dec 2018 12:02:55 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F997130FCA for <i18nrp@ietf.org>; Fri, 7 Dec 2018 12:02:55 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1gVMKo-000BNp-3o; Fri, 07 Dec 2018 15:02:50 -0500
Date: Fri, 07 Dec 2018 15:02:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: Larry Masinter <LMM@acm.org>, "'Asmus Freytag (c)'" <asmusf@ix.netcom.com>, 'Patrik Fältström' <paf=40frobbit.se@dmarc.ietf.org>
cc: i18nrp@ietf.org, 'Paul Hoffman' <paul.hoffman@vpnc.org>
Message-ID: <0D2335F6D932D325C3FBA91E@PSB>
In-Reply-To: <00f301d48e63$071e9be0$155bd3a0$@acm.org>
References: <154385119878.18333.5085298134102919486.idtracker@ietfa.amsl.com> <FF6F9EB9-C73B-4EC0-AC4F-3E3BFBABA0AB@vpnc.org> <8E20D432-01B0-4B52-80BB-3348C5FE73AF@vpnc.org> <CC73FC25-92FC-4822-B267-15C41CE450F2@frobbit.se> <D81CDFF3-8CDF-4168-9CEA-E8DC3A133B73@vpnc.org> <217ede0e-ea1f-bb31-a276-f8c618c71278@ix.netcom.com> <8885EE4C-412E-4337-A099-66354A36CEA1@vpnc.org> <EC12FDAE-4ABD-4AD3-A35A-B39D2C8A0AE0@frobbit.se> <f4417f80-fa86-11e6-baf7-2365981e18b1@ix.netcom.com> <48A2A546-4FEA-4060-8706-34D210B2ABAF@frobbit.se> <055301d48dc8$0ea95120$2bfbf360$@acm.org> <07CB0B3B-E48A-40CD-BBC9-E6CAA2FB29F0@frobbit.se> <001d01d48dee$82b415c0$881c4140$@acm.org> <1f879380-f586-cddf-ae4b-62cfc106308a@ix.netcom.com> <00f301d48e63$071e9be0$155bd3a0$@acm.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/7n0sRozTqMSNegy9ci7CCTZX7js>
Subject: Re: [I18nrp] Last Call: <draft-faltstrom-unicode11-05.txt> (IDNA2008 and Unicode 11.0.0) to Informational RFC
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2018 20:02:57 -0000


--On Friday, December 7, 2018 11:28 -0800 Larry Masinter
<LMM@acm.org> wrote:

>...
> The reason for emphasizing transcription is not that there
> aren't other operations that are possibly more frequent
> (copy/paste a URL from one context to another, remember on a
> bookmark list) but rather that transcription is the most
> stringent requirement – if a user can transcribe a name
> resulting in the same sequence of Unicode codepoints, then
> they can display the name, distinguish the name from other
> (transcribable) names. 

Larry, I hope Asmus will respond further to this because he is
far more expert on relevant issues across a very wide range of
scripts and writing systems than I am, but I don't believe what
you write above is true.  Some scripts --of which the Roman
Script (Basic Latin of some millennia ago) is a good example--
simply have characters that are more easily distinguishable from
either other by people who cannot actually read the script or
associated language(s) that others.  Put a hypothetical person
who has never seen either before in front of a short string of
characters in that script and in front of a script written with
connected characters, complex use of ligatures, and subtle
distinctions among characters (look at Arabic digits for two and
three for an example of what I mean by "subtle" ... or look at
"O" and, in many contemporary type designs, "Q").  Then supply
that person with character pickers for the two scripts.  You
would almost certainly get accurate transcription of the Roman
characters and probably would not get it with the other script.
In neither case would be ability to transcribe imply the ability
to render and display (I'd encourage observation of five and six
year olds learning to write), nor would it imply that ability to
accurately copy and paste.

So, ability to transcribe may be a useful goal, but it isn't,
IMO, close to Patrik's global requirements list.  

best,
   john