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

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 11 July 2007 22:48 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 1I8kz1-0000VX-1u; Wed, 11 Jul 2007 18:48:31 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I8kz0-0000VS-F8 for ltru-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 18:48:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8kz0-0000VJ-4c for ltru@ietf.org; Wed, 11 Jul 2007 18:48:30 -0400
Received: from elasmtp-galgo.atl.sa.earthlink.net ([209.86.89.61]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8kyw-0002lJ-Uy for ltru@ietf.org; Wed, 11 Jul 2007 18:48:30 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=rbfZNOK5+GEZKQAPHFPRN+umh9mGnhwY81SsPY5ETN4vn1+OJRwOFVOKexTAm6Dl; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [64.105.136.50] (helo=oemcomputer) by elasmtp-galgo.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1I8kyV-0007Ft-8H for ltru@ietf.org; Wed, 11 Jul 2007 18:47:59 -0400
Message-ID: <002b01c7c40d$a329e800$6601a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: LTRU Working Group <ltru@ietf.org>
References: <E1I8cnC-0002Sj-7h@megatron.ietf.org><4694E57E.5030909@yahoo-inc.com><DDB6DE6E9D27DD478AE6D1BBBB83579560F3CD6B8B@NA-EXMSG-C117.redmond.corp.microsoft.com> <30b660a20707111413t5cec1d3fs3d6bc83d3852dfa5@mail.gmail.com>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
Date: Wed, 11 Jul 2007 15:48:44 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888fa44b31bb60a9356da05bd9e2d352f1d00896232223c1ce6350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 64.105.136.50
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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

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