Re: [I18nrp] Mappings for IDNA2008 ?

Patrik Fältström <paf@frobbit.se> Fri, 08 February 2019 08:31 UTC

Return-Path: <paf@frobbit.se>
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 636CC1288BD for <i18nrp@ietfa.amsl.com>; Fri, 8 Feb 2019 00:31:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 ee0dl6PMLePP for <i18nrp@ietfa.amsl.com>; Fri, 8 Feb 2019 00:31:23 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21EA41286D8 for <i18nrp@ietf.org>; Fri, 8 Feb 2019 00:31:23 -0800 (PST)
Received: from [IPv6:2a01:3f0:1::9d3b:f506:6996:3459] (unknown [IPv6:2a01:3f0:1:0:9d3b:f506:6996:3459]) by mail.frobbit.se (Postfix) with ESMTPSA id 5713426E7D; Fri, 8 Feb 2019 09:31:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1549614680; bh=4nfA0gvDgMsNkqk+VYetM/Op/sfH/NE4UFmFizxjq1s=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=Y3M5tzM7L9zm9+e4HK9Gkdq96JZhNZImzk04CL2R/osAuGwXWmfRSRIqAhRbt0abY yd77KDShZv5EpCAgMKZlMrQXpTuuDgNj7UMAHgHHdXj+RNQwSlIAyRcgu43ZLJCz6s EsqZrg45N8qeZo3WBqEGqhj75OztSy3fmlMNPhRc=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
X-Mailer: iPad Mail (16E5181f)
In-Reply-To: <bc7b727d-f75c-bbba-4f63-ebd1dcd87085@it.aoyama.ac.jp>
Date: Fri, 8 Feb 2019 09:31:20 +0100
Cc: "i18nrp@ietf.org" <i18nrp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B326FD53-9FE0-4471-B9FF-8A51E9A9B884@frobbit.se>
References: <20190204225047.02583200DC1666@ary.qy> <6660b7e2-1d5b-6a5d-3d1c-55a757e24843@ix.netcom.com> <ADDA4540-9169-4EE6-B33E-3A0D9EED0BD7@frobbit.se> <16ff0d27-9508-7fdd-bc89-9d6fd47396b1@ix.netcom.com> <D5B49CC8-7AEF-4E81-8774-F3F1F05682E8@frobbit.se> <320f4bc3-17b1-595b-34c7-8f95f69c0f33@ix.netcom.com> <B87C6774-4FF7-4A18-A81D-D0834401C293@frobbit.se> <bc7b727d-f75c-bbba-4f63-ebd1dcd87085@it.aoyama.ac.jp>
To: =?utf-8?Q?"Martin_J._D=C3=BCrst"?= <duerst@it.aoyama.ac.jp>
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/LAD3hdtqJo8jZIb7VKsinF6upzI>
Subject: Re: [I18nrp] Mappings for IDNA2008 ?
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, 08 Feb 2019 08:31:25 -0000


> On 8 Feb 2019, at 09:20, Martin J. Dürst <duerst@it.aoyama.ac.jp>; wrote:
> 
> Hello Patrik, others,
> 
>> On 2019/02/08 16:56, Patrik Fältström wrote:
>>> On 5 Feb 2019, at 18:09, Asmus Freytag wrote:
>>> 
>>> OK, if you make the choice that all of this should happen, then what?
>>> 
>>> You'll have to use some tables / algorithm to do the mapping. Even when locale dependent (notionally) you have 90%+ of all cases that are unchanged and some small subset would get adjusted (tailored).
>>> 
>>> That makes providing generic mapping tables useful.
>> 
>> I can as well say it is completely useless for the cases where the mapping *IS* special.
> 
> I don't understand the last sentence. If we take the case of Turkish, 
> then the generic mapping tables are useful because once we have them, a 
> suitable Turkish mapping can be defined as a small delta (e.g. a small 
> preprocessing step) to the generic mapping tables.

lowerCase($string) delivers different result for some strings depending on LOCALE.

That’s what I mean.

   Patrik