Return-Path: <ltru-bounces@lists.ietf.org>
Received: from murder ([unix socket])
	 by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA;
	 Fri, 08 Jul 2005 14:00:53 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 00A7B61B05
	for <harald@alvestrand.no>; Fri,  8 Jul 2005 14:00:52 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
 by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 01407-08 for <harald@alvestrand.no>;
 Fri,  8 Jul 2005 14:00:50 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 3F29761B03
	for <harald@alvestrand.no>; Fri,  8 Jul 2005 14:00:50 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DqrUE-0006k0-6m; Fri, 08 Jul 2005 07:57:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DqrUD-0006jh-93
	for ltru@megatron.ietf.org; Fri, 08 Jul 2005 07:57:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24261
	for <ltru@ietf.org>; Fri, 8 Jul 2005 07:57:38 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqrvY-0000Hm-Eh
	for ltru@ietf.org; Fri, 08 Jul 2005 08:25:57 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24]
	helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44)
	id 1DqrU5-0006jq-0S; Fri, 08 Jul 2005 04:57:33 -0700
Message-Id: <6.2.1.2.2.20050708130647.03e462a0@mail.afrac.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Fri, 08 Jul 2005 13:08:33 +0200
To: "Doug Ewell" <dewell@adelphia.net>,
	"LTRU Working Group" <ltru@ietf.org>
From: r&d afrac <rd@afrac.org>
Subject: Re: [Ltru] Re: status? last call?
In-Reply-To: <00a701c5838a$21e66540$030aa8c0@DEWELL>
References: <20050629114419.FFKU24938.mta8.adelphia.net@megatron.ietf.org>
	<009901c58382$89634a60$030aa8c0@DEWELL>
	<42CE2056.8070408@megared.net.mx>
	<00a701c5838a$21e66540$030aa8c0@DEWELL>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - afrac.org
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
X-BeenThere: ltru@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list
	<ltru.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>,
	<mailto:ltru-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@lists.ietf.org>
List-Help: <mailto:ltru-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>,
	<mailto:ltru-request@lists.ietf.org?subject=subscribe>
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org
X-Virus-Scanned: amavisd-new at alvestrand.no

At 08:56 08/07/2005, Doug Ewell wrote:
>Dylan N. Pierce <dylanpierce at megared dot net dot mx> wrote:
>
> > I note in the descriptions of several tags the use of Unicode code
> > points. (Example: Proven&#xE7;al). I note that Unicode isn't
> > referenced in the document, although draft-10 does reference STD 63.
> >
> > It is obvious to me that those escapes are meant to represent Unicode
> > characters. I just want to make sure that what is obvious to me really
> > is obvious. Forgive me if I'm flaunting my ignorance.
>
>The initial-registry draft refers the reader to the registry-structure
>draft for all details concerning the format and encoding conventions of
>the registry.  The registry-structure draft, in turn, does contain an
>informative reference to Unicode 4.1.0.

This cannot be as this is not an ISO 639-4 accepted reference. Nothing 
protects the IETF which is not an ISO nor a Unicode expert, from conflict. 
As the Chair put it, ISO is ISO and IETF is IETF.
jfc


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