Re: [I18ndir] I18ndir early review of draft-ietf-dispatch-javascript-mjs-07

John R Levine <johnl@taugh.com> Sat, 09 May 2020 16:33 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19023A0B1F for <i18ndir@ietfa.amsl.com>; Sat, 9 May 2020 09:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=YAPPesj+; dkim=pass (1536-bit key) header.d=taugh.com header.b=tk/+tPD1
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 mLR88qtCMpnK for <i18ndir@ietfa.amsl.com>; Sat, 9 May 2020 09:33:28 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 46C4D3A0ACB for <i18ndir@ietf.org>; Sat, 9 May 2020 09:33:27 -0700 (PDT)
Received: (qmail 45712 invoked from network); 9 May 2020 16:33:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=b28c.5eb6db56.k2005; i=johnl-iecc.com@submit.iecc.com; bh=ycEek4r3Ta4NR75VoNE3BwAzzZMB9GdSjGZ33PCUIGU=; b=YAPPesj+Ka0oURnHEBlYNNAzFfGkdaWnpqu2s2xFH7oUh/S415O6p4zxu/2daPZpf++2b8znqR1/hFefPeEhjOJE5aXrBuIa6wW6IQikyiG02Gw58zj2P9k81rkHPjp8tOi7dp55mKHc6jSmVLVnAfNY1KiJpY0BpVsuFDB4nQ6hLx5koFTQJxpjZwRi9TjPtDhTOhdIp6b9EJSsV6VzrAUNhLBFJBIknqcruW2toG9jEMWl1uE9WYjwUi32dW/z
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=b28c.5eb6db56.k2005; olt=johnl-iecc.com@submit.iecc.com; bh=ycEek4r3Ta4NR75VoNE3BwAzzZMB9GdSjGZ33PCUIGU=; b=tk/+tPD1cbilf8O8IsGAHHsYHLRGf492XgkkWXPF0yzwzbk21+6A1vVUZjQQN4D4rw9xBz2EHo7DfSR93oFQh6Nt31S82vn5JZupn/w1eG0JUOKmfZgqorkO6QWINNNV/MEsyrfP/kPQ7SnNlxt7n500/L1J9FUx6AtQZ8vGbZ1UP+P0g1SVylGE5/v6Kr2QYPrrF92IH3OrdESUp28l9HnR/AcS67dk56dfVbKwFedXIJo8bOL//YT2GiV/QfKY
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 09 May 2020 16:33:25 -0000
Date: 9 May 2020 12:33:25 -0400
Message-ID: <alpine.OSX.2.22.407.2005091211170.84818@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: i18ndir@ietf.org
In-Reply-To: <6F916805FF734CB450A3C724@PSB>
References: <158896904545.17044.5288882047334991439@ietfa.amsl.com> <CALaySJ+CRJumYtDCxvGsSwzanz4y=7icuqd+toc0wMivf-mJGg@mail.gmail.c om> <CAD7Fb3diej1-3fAgqZsS_E9wOs1KC=OwVWbvxV5mVjOdQEQm5g@mail.gmail.com> <791ca602-758e-cb0f-a1a4-8fb6b74a8b61@outer-planes.net> <6F916805FF734CB450A3C724@PSB>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/TuQAkAi5LNeyJL7Be1JuxH64bxE>
Subject: Re: [I18ndir] I18ndir early review of draft-ietf-dispatch-javascript-mjs-07
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 May 2020 16:33:31 -0000

> I see nothing in either the body of the document nor in Appendix B that 
> makes it explicit that support for UTF-32 has been dropped.  I think 
> such a comment should be added and explained, even if the explanation is 
> that no one significant is accepting it any more and it is therefore NOT 
> RECOMMENDED and being dropped from the spec.

I agree that a comment saying that UTF-32 is dead as an interchange format 
would be reasonable.

> Noting (again) that, absent a BOM (or even with one) UTF-8
> cannot be reliably distinguished from ISO-8859-X (for any
> registered or unregistered value of X), ...

I'm wondering how much this matters in practice.  I see a lot of 
javascript libraries entirely in ASCII, since non-ASCII characters only 
appear in variable names and in string literals and comments.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly