[Ltru] Re: Solving the UTF-8 problem; was Language Tag Modification 1694acad;
"Doug Ewell" <dewell@roadrunner.com> Tue, 03 July 2007 14:01 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 1I5iwG-0006s2-Tj; Tue, 03 Jul 2007 10:01:08 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I5iwF-0006ri-Gt for ltru-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 10:01:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5iwF-0006rY-6D for ltru@ietf.org; Tue, 03 Jul 2007 10:01:07 -0400
Received: from mta15.mail.adelphia.net ([68.168.78.77] helo=mta15.adelphia.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5iwE-0006Jr-S0 for ltru@ietf.org; Tue, 03 Jul 2007 10:01:07 -0400
Received: from DGBP7M81 ([76.167.184.182]) by mta15.adelphia.net (InterMail vM.6.01.05.04 201-2131-123-105-20051025) with SMTP id <20070703140018.PUGD26470.mta15.adelphia.net@DGBP7M81>; Tue, 3 Jul 2007 10:00:18 -0400
Message-ID: <001201c7bd7a$7c126ab0$6401a8c0@DGBP7M81>
From: Doug Ewell <dewell@roadrunner.com>
To: ietf-languages@iana.org, LTRU Working Group <ltru@ietf.org>
References: <BAY114-F31053BEBAE0817D81180DFB30D0@phx.gbl> <009301c7bd35$1c649a60$6401a8c0@DGBP7M81> <20070703071146.GA8412@nic.fr>
Date: Tue, 03 Jul 2007 07:00:15 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc:
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
Stephane Bortzmeyer <bortzmeyer at nic dot fr> wrote: > 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) There's actually nothing new here, since the Registry is already using Unicode with hex NCRs as the encoding scheme, and we would just be changing it to Unicode with UTF-8 as the encoding scheme. However, it wouldn't hurt to specify NFC somewhere in the draft. This is what we are already using and what the IETF and W3C seem to prefer. Descriptions and comments are supposed to be non-normative, so I'm not sure any user's tools would *have* to do any checking or correcting, though of course ours should. -- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 http://users.adelphia.net/~dewell/ http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Solving the UTF-8 problem; was Language Ta… CE Whitehead
- [Ltru] Re: Solving the UTF-8 problem; was Languag… Doug Ewell
- [Ltru] Re: Solving the UTF-8 problem; was Languag… Stephane Bortzmeyer
- [Ltru] Re: Solving the UTF-8 problem; was Languag… Doug Ewell
- [Ltru] RE: Solving the UTF-8 problem; was Languag… Peter Constable
- [Ltru] RE: Solving the UTF-8 problem; was Languag… Peter Constable