IETF Logo Mail Archive

Re: [I18nrp] Mappings for IDNA2008 ?

"John Levine" <johnl@taugh.com> Tue, 05 February 2019 00:25 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 26FC6130DBE for <i18nrp@ietfa.amsl.com>; Mon, 4 Feb 2019 16:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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=JApG7Lrk; dkim=pass (1536-bit key) header.d=taugh.com header.b=tb9aoFHT
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 htruxsjXd7z5 for <i18nrp@ietfa.amsl.com>; Mon, 4 Feb 2019 16:25:57 -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 2FAC7130E70 for <i18nrp@ietf.org>; Mon, 4 Feb 2019 16:25:56 -0800 (PST)
Received: (qmail 75778 invoked from network); 5 Feb 2019 00:25:55 -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=12800.5c58d813.k1902; bh=lEHGbiCQKb4o5+e1WQsr0GZfbkOlWXB6ihox2tKMPpw=; b=JApG7LrkBHB8Gy8Fv1olvPJWakspMRDkcwZpe+FTJXee5L9SoUJ/9EMyp6ICsOeiESvAaaOMfkjXrlfEjQxgzD+n5QgBADCUrV56CwkeFiFTlxwumjEVHLTpJy8Jn3f7A2y2dd6BoZMBM313nEUzLV8YtE0enTeCNFvKoEMPwOiQSVubROJnn88GjXBJ9+prXcAX8+ImFWmt0r5bLZ3I48kZlN0h+LhJ/0o8sDK1j52Qd97govp0RbjffuwRvPGo
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=12800.5c58d813.k1902; bh=lEHGbiCQKb4o5+e1WQsr0GZfbkOlWXB6ihox2tKMPpw=; b=tb9aoFHT7c3Zis/guZnzc3UFdxOBQtbQqsgyPPml2OguxS7CY6smRVKuBc5cOy2w5Z5QBaNKK85rUOhwOQc40GbVt5ONCAPP+HEkvKIcFByKb2d5gcfqtS62D4YKQn5GA7xb0AXN0UPNPOk3PXHvLgvMAstfML3Txg92ViSdmftOXaL8bCzeJv6dAfPbHGMfG3rBaYu938NLBjZQTaLBZgIy6dUXI4V2MxLwbinSkh1Rpplinahl6+woXOPqRzjr
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; 05 Feb 2019 00:25:55 -0000
Received: by ary.qy (Postfix, from userid 501) id 1AFBA200DC1DB1; Mon, 4 Feb 2019 19:25:54 -0500 (EST)
Date: Mon, 04 Feb 2019 19:25:54 -0500
Message-Id: <20190205002555.1AFBA200DC1DB1@ary.qy>
From: John Levine <johnl@taugh.com>
To: i18nrp@ietf.org
Cc: asmusf@ix.netcom.com
In-Reply-To: <6660b7e2-1d5b-6a5d-3d1c-55a757e24843@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/a4ahBjBAK7-raM-Q3BHSekEu6M8>
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:26:05 -0000

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

v2.23.0 | Report a Bug | By Email