[Ltru] Wrapping up the UTF-8 debate

"Randy Presuhn" <randy_presuhn@mindspring.com> Fri, 20 July 2007 16:19 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 1IBvCu-0001vc-0w; Fri, 20 Jul 2007 12:19:56 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IBvCs-0001vP-Hg for ltru-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 12:19:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBvCs-0001vH-8G for ltru@ietf.org; Fri, 20 Jul 2007 12:19:54 -0400
Received: from elasmtp-banded.atl.sa.earthlink.net ([209.86.89.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBvCq-0002SP-TH for ltru@ietf.org; Fri, 20 Jul 2007 12:19:54 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Rn1/WBddqs2PpSy0zIXAiPuY6/tI4zmr6LaxR3dQg5o//iCLZZ0lX1BDTPErMc08; 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 [68.164.80.181] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IBvCq-0005zD-AR for ltru@ietf.org; Fri, 20 Jul 2007 12:19:52 -0400
Message-ID: <011701c7cae9$f23811a0$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: LTRU Working Group <ltru@ietf.org>
References: <002c01c7ca8b$076f2d60$6a01a8c0@DGBP7M81><46A049B5.2050800@yahoo-inc.com><20070720060014.GQ5737@mercury.ccil.org> <46A052B8.3060508@yahoo-inc.com>
Date: Fri, 20 Jul 2007 09:20:52 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888fa44b31bb60a9356dba72236f500c0c6922903cf06bd9efb350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.80.181
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Subject: [Ltru] Wrapping up the UTF-8 debate
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...

> From: "Addison Phillips" <addison@yahoo-inc.com>
> To: "John Cowan" <cowan@ccil.org>
> Cc: "Doug Ewell" <dewell@roadrunner.com>; "LTRU Working Group" <ltru@ietf.org>
> Sent: Thursday, July 19, 2007 11:14 PM
> Subject: Re: [Ltru] Draft-4645bis-01 expires
...
> This editor, please note, is growing annoyed with the on-and-off nature 
> of the UTF-8 argument. I wish verily that the chairs would determine a 
> consensus or lack thereof.
...

Unfortunately, the technical discussion has thus far not worked through
all of the key points that need to be addressed before it makes sense
for us to declare a consensus.  Several decompositions of the issues
have been presented, but as I see it these are the related questions
that must *all* be answered before we can declare a consensus on this
bundle of issues called the "UTF-8 argument."

   1)  Are we willing to use a representation (for the discussion
       of changes on the ietf-languages@iana.org list and communication
       with IANA) which is different (perhaps only mechanically/trivially so)
       from what is actually published in the registry files?

   2)  The registry file itself currently uses something which is similar
       to an NCR.  Are we willing to change the registry format to
          a) use actual NCRs for non-ASCII code points, making conversion
             to XML even more trivial than it already is, while still
             giving some fallback to folks inspecting the data for errors
             or looking at it through ASCII windows
          b) embed the actual (UTF-8 encoded) characters into the file
          c) something else?

   3)  Are we going to instruct IANA to maintain a "pure" ASCII version
       of the registry, in which everything not ASCII will have been flattened
       or translitered?

My sense of the discussion so far is that folks are OK with (1), and that
(3) won't have enough support to justify the cost.  The part that still needs
to be hashed out is the choice between (2a), (2b) and (2c).

So, please, let's wrap this up.  To me this means:

Determining what we need to say about (1) in 4646bis.
Making a choice from the various options in (2).
Agreeing that (3) is not our problem.

Randy
          



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