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

Addison Phillips <addison@yahoo-inc.com> Wed, 11 July 2007 14: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 1I8cwk-00059e-Uj; Wed, 11 Jul 2007 10:13:38 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I8cwh-00059J-9O for ltru-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 10:13:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8cwg-00059A-Vk for ltru@ietf.org; Wed, 11 Jul 2007 10:13:34 -0400
Received: from rsmtp2.corp.yahoo.com ([207.126.228.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8cwc-0001JE-Il for ltru@ietf.org; Wed, 11 Jul 2007 10:13:34 -0400
Received: from [10.72.76.224] (snvvpn2-10-72-76-c224.corp.yahoo.com [10.72.76.224]) (authenticated bits=0) by rsmtp2.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l6BEDISf003060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jul 2007 07:13:19 -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=nARGfvprKTODTDJFNAuZGzQdWy97gUvzvfSudTILrqzhawFNB/RKAHtQenuv1fju
Message-ID: <4694E57E.5030909@yahoo-inc.com>
Date: Wed, 11 Jul 2007 07:13:18 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Debbie Garside <debbie@ictmarketing.co.uk>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
References: <E1I8cnC-0002Sj-7h@megatron.ietf.org>
In-Reply-To: <E1I8cnC-0002Sj-7h@megatron.ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
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

Voting isn't the measure: rough consensus is the measure. I agree that a 
strawpoll would help establish if we have consensus, though.

I, of course, have always supported putting the registry into UTF-8. If 
folks are happy with the resolution to the parser compatibility issue, 
I'm happy to go to UTF-8.

So:

+1

Addison

Debbie Garside wrote:
> Couldn't we just put it to the vote?  I thought we had this discussion a
> year or so ago?
> 
> FWIW, my vote would be +1
> 
> Best regards
> 
> Debbie 
> 
>> -----Original Message-----
>> From: Peter Constable [mailto:petercon@microsoft.com] 
>> Sent: 10 July 2007 17:20
>> To: LTRU Working Group; ietf-languages@iana.org
>> Subject: RE: [Ltru] Re: Solving the UTF-8 problem
>>
>>> From: Chris Newman [mailto:Chris.Newman@Sun.COM]
>>
>>> UTF-8 has been the recommend charset for Internet interchange since 
>>> RFC 2277.
>>> Our past experience with ASCII encodings of non-ASCII text 
>> in the IETF 
>>> has been questionable... Meanwhile, UTF-8 based IETF protocols have 
>>> been less problematic from an interoperability viewpoint...
>> Sound to me like good arguments for us to be considering 
>> UTF-8 for the LSTR.
>>
>>
>>
>> Peter
>>
>>
>> _______________________________________________
>> Ltru mailing list
>> Ltru@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ltru
>>
>>
> 
> 
> 
> 
> 
> _______________________________________________
> 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