IETF Logo Mail Archive

Re: [I18nrp] Conservatism principle doesn't go far enough

"John Levine" <johnl@taugh.com> Mon, 04 February 2019 01:48 UTC

Return-Path: <johnl@iecc.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 86BC4130DE4 for <i18nrp@ietfa.amsl.com>; Sun, 3 Feb 2019 17:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-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=kfZru5yr; dkim=pass (1536-bit key) header.d=taugh.com header.b=AEgB3LQS
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 szYmn24Xfnto for <i18nrp@ietfa.amsl.com>; Sun, 3 Feb 2019 17:48:16 -0800 (PST)
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 D717D126F72 for <i18nrp@ietf.org>; Sun, 3 Feb 2019 17:48:15 -0800 (PST)
Received: (qmail 4104 invoked from network); 4 Feb 2019 01:48:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1006.5c5799df.k1902; bh=W3XI/0nvRJgB9k+SSuSZ1EL/gVXzaKlaC3TsYO2a9HY=; b=kfZru5yr+uGgWUwiHQSeSka4dTUOmfRMZum65C/Ie/rnL5BnybcwtRNypj7Lai8NZ8H7HDoxY4PYfX3JWaGYblSyr9WftvKLaCt+XSI0bizm5W+DYyz32sDOtqrQeE6ILoYqUNJhWG9qeJx2jnwnG2DTnpWysZKDPadIxTyeAUTxohoMmaP0MAfRQSpaxuRKp33Mqw5BURG889IdH503bHendu/z2Tzb6FhsZyl4BDnH3KCuRt6VOtJAT5AoI9Gc
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1006.5c5799df.k1902; bh=W3XI/0nvRJgB9k+SSuSZ1EL/gVXzaKlaC3TsYO2a9HY=; b=AEgB3LQSruxyK+9osHPsY4mR7qU1/hw6SaNktUufHpxgJlXC/Yklu+M2A8GONcESUlkyn+AlxJVTHA0mtfswZDR+P8iDmyqW7OnoyLFt55KSwzVal2WYS/OlTzykcd3sbOGOjQLdBUxPq3gcMYEOdmguh4Ai2Wm41okGrNvnhL6CwV3pp+dH1bY61/2DVpc939h4HVzObbLM8M3QKawu9bPcIT7rtLIuqQRV5bbGtnpkhON+yQHeR7Wp8ZTJ+8Ub
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 04 Feb 2019 01:48:14 -0000
Received: by ary.qy (Postfix, from userid 501) id 90BD9200DB93A4; Sun, 3 Feb 2019 20:48:13 -0500 (EST)
Date: Sun, 03 Feb 2019 20:48:13 -0500
Message-Id: <20190204014814.90BD9200DB93A4@ary.qy>
From: John Levine <johnl@taugh.com>
To: i18nrp@ietf.org
Cc: asmusf@ix.netcom.com
In-Reply-To: <a956b63b-cff0-5df3-b7fc-511274542349@ix.netcom.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/_p-Ab_Skia2qscWt7u7XBaeUk5E>
Subject: Re: [I18nrp] Conservatism principle doesn't go far enough
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: Mon, 04 Feb 2019 01:48:17 -0000

In article <a956b63b-cff0-5df3-b7fc-511274542349@ix.netcom.com> you write:
>-=-=-=-=-=-
>
>On 2/2/2019 8:01 PM, Larry Masinter wrote:
>> But I think this is counter-productive and wrong. If you're showing someone
>> a URL which is not in normal form, normalization will lose this critical
>> information. Better to just display the punicode for any unnormalized
>> domains.
>
>I'm missing something here. What "critical" information (other than the 
>normalization state) is it that gets lost?

It seems to me that by the time text makes it into a URL that comes
from a web page or similar source, if it's not normalized, somthing
rather peculiar is going on.

>There are some scripts where ordinary text is most likely not normalized 
>and where it's also not necessarily trivial for users to enter 
>normalized text. Should all of those URLs get displayed as punycode?

I believe that normalizing user input is a separate issue.  Of course
you normalize what the user typed before using it.

R's,
John

v2.23.0 | Report a Bug | By Email