[Ltru] Re: Solving the UTF-8 problem; was Language Tag Modification 1694acad;

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 03 July 2007 07:12 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5cZC-0001qK-Tv; Tue, 03 Jul 2007 03:12:55 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I5cZC-0001mJ-0m for ltru-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 03:12:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5cZ8-0001lQ-9a for ltru@ietf.org; Tue, 03 Jul 2007 03:12:50 -0400
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5cY9-0006CL-01 for ltru@ietf.org; Tue, 03 Jul 2007 03:12:49 -0400
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 88F991C00DF; Tue, 3 Jul 2007 09:11:48 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 833861C00F6; Tue, 3 Jul 2007 09:11:46 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 7F98C58ECCA; Tue, 3 Jul 2007 09:11:46 +0200 (CEST)
Date: Tue, 03 Jul 2007 09:11:46 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Doug Ewell <dewell@roadrunner.com>
Message-ID: <20070703071146.GA8412@nic.fr>
References: <BAY114-F31053BEBAE0817D81180DFB30D0@phx.gbl> <009301c7bd35$1c649a60$6401a8c0@DGBP7M81>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <009301c7bd35$1c649a60$6401a8c0@DGBP7M81>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-4-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf-languages@iana.org, LTRU Working Group <ltru@ietf.org>
Subject: [Ltru] Re: Solving the UTF-8 problem; was Language Tag Modification 1694acad;
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

On Mon, Jul 02, 2007 at 10:43:39PM -0700,
 Doug Ewell <dewell@roadrunner.com> wrote 
 a message of 74 lines which said:

> Can we pursue this official version/unofficial version strategy, as
> an alternative to loading up the Registry with excise?

It seems a good strategy, very "better to light a candle than to
complain about obscurity".

I would say -1 to any decision of having *several* official versions
(because it would be more work for IANA and more opportunity to have a
discrepancy, something which is not serious with unofficial versions,
but could be dramatic between official versions).

But allow me a little troll: if we choose UTF-8, what about
normalization?

1) Do not mention it (this would mean that IANA would be free to
suddenly canonicalize the registry, thus making it different in a
byte-to-byte comparison)

2) Mandate NFC or NFD (which means an automatic registry checker would
have to check it)



_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru