IETF Logo Mail Archive

Re: [I18nrp] next steps

Asmus Freytag <asmusf@ix.netcom.com> Tue, 24 July 2018 03:38 UTC

Return-Path: <asmusf@ix.netcom.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 1CC2C130DFE for <i18nrp@ietfa.amsl.com>; Mon, 23 Jul 2018 20:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ix.netcom.com; domainkeys=pass (2048-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.com
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 LeIuVfM96EAX for <i18nrp@ietfa.amsl.com>; Mon, 23 Jul 2018 20:38:17 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (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 825201271FF for <i18nrp@ietf.org>; Mon, 23 Jul 2018 20:38:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ix.netcom.com; s=dk12062016; t=1532403693; bh=nvbbz14IWZW6ZdFyhekm1UbkGhPcF2dyc9q/ XlUT4vQ=; h=Received:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=pVvDaxUa6jlK73gN4JykCS/16wp7nHtDU gO5klveE5+ZTo9iUJGY7LSW68zQWu3C2XnkWOLCw6GfBtSx0GEefbMcawc7Rkc/AEpy jESe3FrfgDKt4sGgGIKpfltA/RGR1Pv+TNqqTyWiLZ8ldEAem46t29q4YBZ9Mw4vkWk eD7TBReK4u6Mlc/nihV+HS9qGYZRrach2qFcbinz31/LSUmbsgPuXDfU+DERef9REDy Mf9MJsq0AhAryCEhjQ9gVbKwrYw68+2HQc8CTc80kZShgZvdHVZAdjRHtjezVIcKJmQ l2hoFzBsKSbuiOKRIuunace5mZCoTpSBnaSEW2PPQ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=ix.netcom.com; b=Ik7+CEOR0U0Ck/SKFmHF+V15w4sefldI8L8XrrIuuJxNKonipXP0KlYQV4jLh43nFqWWjC+oHT3N+7QQ59ZhRv/P/iy4FqIbbl7xruDMXTtvveHH+NWMsA3JaLcMj+Mh1bjtJnitbIZuRQdjbmsXh+dS8cTr9v41pRKKTekJJlhfclgc/oCFynNEVZ+gKC95anE3kQhPAf0K+gwHv0ivwfB3mXjFSZiW+QNHKlaj8OOfBMVwA54eCoZzOZwgiM+gE5uxpFipjxqP7GadXBaE+lb6HD9ro+7AMibI95d6G+XqOiyCh+8e7SPkj6qdueYyQr7LOqTGj0SFBJYvJnwruw==; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [174.21.163.1] (helo=[192.168.0.5]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <asmusf@ix.netcom.com>) id 1fhoCY-0006WL-PG for i18nrp@ietf.org; Mon, 23 Jul 2018 23:41:30 -0400
To: i18nrp@ietf.org
References: <E10F785F-39A8-4A03-B5F0-0672B806B440@vpnc.org> <de326e16-8f93-7afd-0090-06ee7e672471@stpeter.im> <5b569782.1c69fb81.4603.51f9@mx.google.com>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <9c81fb76-e4cd-a9d7-eded-960256f224ec@ix.netcom.com>
Date: Mon, 23 Jul 2018 20:38:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <5b569782.1c69fb81.4603.51f9@mx.google.com>
Content-Type: multipart/alternative; boundary="------------3BF61BFB3BDF423C8BD390CD"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b7eec10b52094b3e7d6b7989330a987414c537cee3b4b614350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 174.21.163.1
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/_qEgf5YK5IdOVxTs5Hv9owhXp8U>
Subject: Re: [I18nrp] next steps
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 24 Jul 2018 03:38:20 -0000

On 7/23/2018 8:05 PM, Larry Masinter wrote:
>
> Is it time to talk about specific drafts?
>
> This seems more general:
>
> There is a problem in RFC 6365 “Terminology used…” that I think is at 
> the core: It seems to imply that the way to compute equivalence of 
> strings REQUIRES normalization to allow determining a~b iff 
> normalize(a)==normalize(b).
>
> But in general, the equivalence relations one might want, for 
> usability reasons, don’t have an acceptable normal form.
>
> Continuing to put in normalization as an essential step is doomed to 
> failure. Some protocols may need to be redefined to allow 
> non-normalized strings.
>

If you define equivalence relations (e.g. variants) based on code 
points, then you'll need to apply these / compare strings in NFD 
otherwise you will miss out on the effect of re-ordering of combining 
sequences.

Separate from that are equivalences between sequences so that some 
distinctions that are never normalized away can be treated as 
equivalent. For example some ordering differences in complex scripts.

A./
>
> --
> http://LarryMasinter.net
>
>
>
> _______________________________________________
> i18nRP mailing list
> i18nRP@ietf.org
> https://www.ietf.org/mailman/listinfo/i18nrp

v2.8.7 | Report a Bug | By Email