Re: [Ltru] Re: Solving the UTF-8 problem

Addison Phillips <addison@yahoo-inc.com> Wed, 11 July 2007 23:13 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 1I8lNO-0005CR-66; Wed, 11 Jul 2007 19:13:42 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I8lNN-0005CE-19 for ltru-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 19:13:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8lNM-0005C6-Ni for ltru@ietf.org; Wed, 11 Jul 2007 19:13:40 -0400
Received: from rsmtp2.corp.yahoo.com ([207.126.228.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8lNI-0002Ip-AO for ltru@ietf.org; Wed, 11 Jul 2007 19:13:40 -0400
Received: from [10.72.73.3] (snvvpn1-10-72-73-c3.corp.yahoo.com [10.72.73.3]) (authenticated bits=0) by rsmtp2.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l6BNDTIb057954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jul 2007 16:13:32 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=D6PuA/GeLenGzTNhWeHBCtF0toF8PAtLgtbf3ADKi41aDrQcXwABZLKO+8HUz3F3
Message-ID: <46956417.5030509@yahoo-inc.com>
Date: Wed, 11 Jul 2007 16:13:27 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
References: <E1I8cnC-0002Sj-7h@megatron.ietf.org><4694E57E.5030909@yahoo-inc.com><DDB6DE6E9D27DD478AE6D1BBBB83579560F3CD6B8B@NA-EXMSG-C117.redmond.corp.microsoft.com> <30b660a20707111413t5cec1d3fs3d6bc83d3852dfa5@mail.gmail.com> <002b01c7c40d$a329e800$6601a8c0@oemcomputer>
In-Reply-To: <002b01c7c40d$a329e800$6601a8c0@oemcomputer>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: LTRU Working Group <ltru@ietf.org>
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

 > The devil is frequently in the details, so we can't declare
 > consensus here until we've worked throught the rest of the exorcise.

Understandable, although, pace any showstoppers, the question currently 
is whether there is consensus toward pursuing this course.

Here's my thought on "order of battle": I will prepare the current text 
and submit it tomorrow.

Then I will incorporate the various pending bits of text plus the 
necessary changes for UTF-8 into a new prototype draft, which I will 
publish on inter-locale.com. When the ID Editors publish the draft 
mentioned just above, I'll submit this new draft. Given their recent 
history of prompt action, this could even be sometime Friday. This would 
give us a basis for diff comparisons [and XML2RFC source] (in case we 
decide to revert Yet One More Time).

Since I've already done this exercise once, it shouldn't prove to be 
that difficult.

NB> Doug will need to add instructions in 4645 about how he's converting 
hex escapes in the original registry to Unicode.

Addison


Randy Presuhn wrote:
> Hi -
> 
> As a co-chair...
> 
> There appears to be an emerging consensus that having UTF-8 in the
> registry would make sense.  Before we can claim to have completed
> this item, however, we should identify and get agreement on updated
> text for 4646bis to make it so, as well as any additional
> instructions for the conversion and "bulk update" of the registry
> itself.  The devil is frequently in the details, so we can't declare
> consensus here until we've worked throught the rest of the exorcise.
> 
> Randy
> 
> 
> 
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.


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