Re: [I18nrp] Mappings for IDNA2008 ?

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 05 February 2019 00:40 UTC

Return-Path: <ajs@anvilwalrusden.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 998A0130DF1 for <i18nrp@ietfa.amsl.com>; Mon, 4 Feb 2019 16:40: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=GiNFxtlB; dkim=pass (1024-bit key) header.d=yitter.info header.b=JlugxgA+
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 VX5sw6JGUaCo for <i18nrp@ietfa.amsl.com>; Mon, 4 Feb 2019 16:40:55 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23D82130DD6 for <i18nrp@ietf.org>; Mon, 4 Feb 2019 16:40:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 17873BB840; Tue, 5 Feb 2019 00:40:54 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1549327254; bh=RQtdy3NR3xEG+bzsFJ22NzNiOum69AMDRFdE84399KE=; h=From:To:CC:Date:In-Reply-To:References:Subject:From; b=GiNFxtlB3XnJiEu3LaUUMUn5AOcfO7l5Ck1SeK3qybwBhevJo3w3NhCrmDERyfaKp chJY6cVeOcSfeAI2Lb4vZ6OP8Z8U79dNLrTLQlS/yPUSN8XgsO4Ppy42f69ApFKjQP lOEXZfu2F8r6dtoz0ViJhnOFwxFFZh+9LUKDrpiE=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80zH8jz_9kMQ; Tue, 5 Feb 2019 00:40:53 +0000 (UTC)
From: Andrew Sullivan <ajs@anvilwalrusden.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1549327253; bh=RQtdy3NR3xEG+bzsFJ22NzNiOum69AMDRFdE84399KE=; h=From:To:CC:Date:In-Reply-To:References:Subject:From; b=JlugxgA+Ll+SfzcD0eIl12BrzMWfPzJYZuRKmhRlsvNEgNgkL0n5ZfB7ZSDawjT/F 5vgWAF1PiIT5MEjS3jzeSSxFHmlgO4oqfMB5na3EPLw63uJHWtR2Rq8RvGdN2d7e4H Ty1cfm+bqhjXQgUQObtM4Hx8JAxuL1hOs6WqQ1mk=
To: John Levine <johnl@taugh.com>, <i18nrp@ietf.org>
CC: <asmusf@ix.netcom.com>
Date: Mon, 04 Feb 2019 19:40:50 -0500
Message-ID: <168bb19ae68.278b.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
In-Reply-To: <20190205002555.1AFBA200DC1DB1@ary.qy>
References: <20190205002555.1AFBA200DC1DB1@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/-Uv_MZrqQoHBmk9lwZZhkf-94Ac>
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: Tue, 05 Feb 2019 00:40:58 -0000

And some of this, of course, is the result of attempts to be backward 
compatible with IDNA2003, when the WG consensus was to have a transition 
that fixed the problems in 2003.  The decision of UTS46 is really to have 
that transition last essentially forever. This is, I suspect, a difference 
in taste between the ietf and UTC communities about how to make those 
trade-offs, but it has created part of the problem.

A
--
Andrew Sullivan
Please excuse my clumbsy thums.

On February 4, 2019 19:26:21 "John Levine" <johnl@taugh.com>; wrote:

> In article <6660b7e2-1d5b-6a5d-3d1c-55a757e24843@ix.netcom.com>; you write:
>>> Are there any published IDNA2008 mappings?  As far as I can tell,
>>> everyone uses one from UTS46 by default, and it's not very good.
>> Examples of its badness, please.
>
> As I understand it:
>
> If you speak Turkish, the case folding is wrong.
>
> If you speak Persian, the joiners are wrong.
>
> If you speak Arabic, the mapping or lack thereof between
> ASCII and Arabic digits is often wrong.
>
> If you speak Chinese, the whole thing is wrong because Chinese users
> expect their ASCII pinyin to be turned into Chinese.
>
> IDNA 2008 said very clearly that good mappings depend on the user's
> context, with the language being a large part of that context.
>
> R's,
> John
>
> _______________________________________________
> i18nRP mailing list
> i18nRP@ietf.org
> https://www.ietf.org/mailman/listinfo/i18nrp