Re: [I18nrp] Mappings for IDNA2008 ?

"John Levine" <johnl@taugh.com> Fri, 08 February 2019 17:58 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 055D01294FA for <i18nrp@ietfa.amsl.com>; Fri, 8 Feb 2019 09:58:18 -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=pV5cQPzM; dkim=pass (1536-bit key) header.d=taugh.com header.b=VqZohiUc
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 Kw0DXmPDxR7O for <i18nrp@ietfa.amsl.com>; Fri, 8 Feb 2019 09:58: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 D63F4124BF6 for <i18nrp@ietf.org>; Fri, 8 Feb 2019 09:58:15 -0800 (PST)
Received: (qmail 21756 invoked from network); 8 Feb 2019 17:58:14 -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=54fa.5c5dc336.k1902; bh=IxsCsw91Tv2aKFVNizgvktZ3+wfdxSkjErlRPFs08Vw=; b=pV5cQPzMEfVEZCKRtXYcL3OPsN2di1ulbwxgjs8ng/Mp15Y9i6ehnw8TLsuVfwIlzTcKU7NBaIRewGmZwHuPfnuDhJtXPEo71BC/AM9tW7rH51d2NoWJmeQfipvb0JmUWAb2Qs+MpxVi5XUGyT7zReORyj9V6rUkWU4TgdTG5sCz80pc4HQ89apOxn8zGbEv73gwMATgPStQXCGghP4azFm3y3qvLDvWt0CwUKuPhL3p6m6o8PsHGP81F5i31GRp
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=54fa.5c5dc336.k1902; bh=IxsCsw91Tv2aKFVNizgvktZ3+wfdxSkjErlRPFs08Vw=; b=VqZohiUcAkfMCZXkvNcauJdVESvA/70WU9wY3cQizN7dDYWeywLEh3ewgO8MCcJyfe4FyVnci22lIqzod7xNhwXii+I+pLIupNJ7zvcuyAMt0NlVcTYxFzNAie/OLD5e+M/FIg920I4diZkpym7vnOm1dMOhfAm6gufFVCos8Cpp7ugTE/OjD+oL21XUlY+eux3oKrF+JLLfARydjJ08cBc82aaAfJcBVY9gkK0lZppVA/k20Mnx6hwnUUi3rcSy
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; 08 Feb 2019 17:58:13 -0000
Received: by ary.qy (Postfix, from userid 501) id C59D8200DFCD52; Fri, 8 Feb 2019 12:58:13 -0500 (EST)
Date: 8 Feb 2019 12:58:13 -0500
Message-Id: <20190208175813.C59D8200DFCD52@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: i18nrp@ietf.org
Cc: duerst@it.aoyama.ac.jp
In-Reply-To: <bc7b727d-f75c-bbba-4f63-ebd1dcd87085@it.aoyama.ac.jp>
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/obaLzGXnVgXCK9C77twThrCktws>
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 17:58:18 -0000

In article <bc7b727d-f75c-bbba-4f63-ebd1dcd87085@it.aoyama.ac.jp>; you write:
>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.

That would be great if the small delta tables actually exist.  But
they don't.  It's been a decade since IDNA2008 and I have yet to see
any language-specific mappings at all.

I agree that the mapping tables for languages written in Latin
characters will mostly be the same, but it's the differences that
cause problems.  Software that works most of the time not the same as
software that works.