IETF Logo Mail Archive

[Ltru] Re: draft-4645bis-03

"Doug Ewell" <dewell@roadrunner.com> Fri, 14 December 2007 17:36 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 1J3ET0-0000jh-K4; Fri, 14 Dec 2007 12:36:54 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1J3ESy-0000gW-Rb for ltru-confirm+ok@megatron.ietf.org; Fri, 14 Dec 2007 12:36:52 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3ESy-0000gO-Go for ltru@ietf.org; Fri, 14 Dec 2007 12:36:52 -0500
Received: from mta16.adelphia.net ([68.168.78.211]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3ESy-00042e-2N for ltru@ietf.org; Fri, 14 Dec 2007 12:36:52 -0500
Received: from DGBP7M81 ([76.167.184.182]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20071212155708.HYTA23096.mta10.adelphia.net@DGBP7M81>; Wed, 12 Dec 2007 10:57:08 -0500
Message-ID: <002701c83cd7$a6200290$6601a8c0@DGBP7M81>
From: Doug Ewell <dewell@roadrunner.com>
To: LTRU Working Group <ltru@ietf.org>
References: <000301c83b00$e828dcd0$6601a8c0@DGBP7M81> <20071211165939.GA13871@laperouse.bortzmeyer.org> <001301c83c84$bdc47e60$6601a8c0@DGBP7M81> <20071212092410.GB14869@nic.fr>
Date: Wed, 12 Dec 2007 07:57:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
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.3198
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc:
Subject: [Ltru] Re: draft-4645bis-03
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

Stéphane Bortzmeyer <bortzmeyer at nic dot fr> wrote:

>> In fact, draft-4646bis makes no provision for "optional" hex NCRs, 
>> only UTF-8.
>
> Thanks for the reminding. My tool currently converts the NCR to 
> Unicode. Should I stop?

A tool that is intended to check the Registry for conformance to the 
spec should stop.

A tool that is intended for practical use in language tagging might 
choose to be robust and continue to interpret hex NCRs, so it will work 
with both old and new versions of the Registry.  This would backfire if 
a subtag were added with a Description or Comments field containing a 
sequence that looked like a hex NCR, which would be a supremely bad 
idea.

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://home.roadrunner.com/~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

v2.23.0 | Report a Bug | By Email