Re: [Ltru] Re: UTF-8

Addison Phillips <addison@yahoo-inc.com> Sun, 17 September 2006 22:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GP5bS-0000wb-Hd; Sun, 17 Sep 2006 18:59:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GP5bR-0000wU-Bp for ltru@ietf.org; Sun, 17 Sep 2006 18:59:09 -0400
Received: from rsmtp2.corp.yahoo.com ([207.126.228.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GP5bN-00056E-Vd for ltru@ietf.org; Sun, 17 Sep 2006 18:59:09 -0400
Received: from [10.72.76.233] (snvvpn2-10-72-76-c233.corp.yahoo.com [10.72.76.233]) (authenticated bits=0) by rsmtp2.corp.yahoo.com (8.13.6/8.13.6/y.rout) with ESMTP id k8HMwsFn003362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Sep 2006 15:58:55 -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=JmvR7cgK3Z1vxn4QEVC/+zHtR8hQNotqfpZFp2uxNRuLMu25N3DjbJWujVvUj+pq
Message-ID: <450DD32E.5060604@yahoo-inc.com>
Date: Sun, 17 Sep 2006 15:58:54 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: John Cowan <cowan@ccil.org>
Subject: Re: [Ltru] Re: UTF-8
References: <789E617C880666438EDEE30C2A3E8D10EEFC@mailsrvnt05.enet.sharplabs.com> <450B2B75.2F36@xyzzy.claranet.de> <6.0.0.20.2.20060916114849.081056e0@localhost> <450BD347.9EA@xyzzy.claranet.de> <6.0.0.20.2.20060917154808.08a12880@localhost> <20060917183821.GC26073@ccil.org> <450DA2D1.6020706@yahoo-inc.com> <20060917210513.GF26073@ccil.org>
In-Reply-To: <20060917210513.GF26073@ccil.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 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

> 
>> But that consideration doesn't apply to the registry file. It only 
>> applies to the discussion of a registry entry on ietf-languages. 
>> Admittedly MUAs vary greatly in their support for encodings, but we can 
>> certainly specify directions for how to send the registration request to 
>> the list so that everyone can tell what code points are intended and 
>> other instructions for how to encode those characters in the registry.
> 
> Directions which work uniformly across all native encodings, operating
> environments, and mailers?  I venture to doubt it.
> 

Uh... how about something like "in your registration form, non-ASCII 
code points must be encoded as an XML-like NCR"

I didn't say that the registration forms had to support non-ASCII. Only 
that it be possible for everyone to tell what the code points were 
supposed to be and for IANA to arrive at a UTF-8 registry from them.

Addison

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.

Internationalization is an architecture.
It is not a feature.

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