Re: [Ltru] UTF-8

Addison Phillips <addison@yahoo-inc.com> Thu, 21 June 2007 20:02 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 1I1SrH-0008KG-7o; Thu, 21 Jun 2007 16:02:23 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I1SrF-0008J8-RT for ltru-confirm+ok@megatron.ietf.org; Thu, 21 Jun 2007 16:02:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Shd-0000kW-B0 for ltru@ietf.org; Thu, 21 Jun 2007 15:52:25 -0400
Received: from rsmtp1.corp.yahoo.com ([207.126.228.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1ShS-0002bu-Ry for ltru@ietf.org; Thu, 21 Jun 2007 15:52:25 -0400
Received: from [172.21.148.31] (wlanvpn-mc2e-246-31.corp.yahoo.com [172.21.148.31]) (authenticated bits=0) by rsmtp1.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l5LJqAWI085090 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jun 2007 12:52:10 -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=kofcGxwXRon2c2fbNH23Qo/gWGnHz5fs642DoZVn+L6ODQClcweOulgNgGKTRiVV
Message-ID: <467AD6E9.6020809@yahoo-inc.com>
Date: Thu, 21 Jun 2007 12:52:09 -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] UTF-8
References: <467ABA07.5010306@gmail.com><20070621180158.GC9078@mercury.ccil.org><41a006820706211153r45ef3094p169901d87cb910d4@mail.gmail.com> <20070621185738.GE9078@mercury.ccil.org> <001201c7b43b$970e10a0$6601a8c0@oemcomputer>
In-Reply-To: <001201c7b43b$970e10a0$6601a8c0@oemcomputer>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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

I think we should close this discussion. We're unlikely to make it 
further this time than last. I think UTF-8 is desirable and the 
procedural points can be solved to deal with it. But I don't think we'll 
find consensus down this path (or at least consensus that doesn't have 
multiple loud objections). Ditto on the XML proposal.

Addison

Randy Presuhn wrote:
> Hi -
> 
> As co-chair...
> 
> We've had this discussion  several times.  As long as there is
> an insistance that the format for the communication of updates
> is the same as that of the registry itself, I'm pretty sure the conclusion
> won't change in the forseeable future.  Just on this list, we've all
> seen the picturesque results of various incompatible mailers
> (and even different configurations of the same mailer) mangling
> what should be simple UTF-8.  Unfortunately, it doesn't appear to
> just be a question of having the right fonts.
> 
> If this thread is to move forward to a different conclusion, the only
> path by which I can see it succeeding is to recognize that the
> email communication of changes might have to rely on a different
> coding of non-ASCII things from what the registry itself uses.
>  If we can agree that the existing email format is adequate for purposes
> of communicating changes, then there are three decisions needed:
>     (0) do we want to stick with email as our mechanism for communicating
>           updates?
>    (1) is a UTF-8 registry indeed desirable?
>    (2) if so, are we willing to allow IANA to convert the apropriate bits
>         of an update directive conveyed in ASCII into the "real" code points?
> 
> But please, let's not rehash the discussion we've already had.
> 
> 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