Re: [Ltru] UTF-8 in which field? (Was: draft-ietf-ltru-4646bis-07

Addison Phillips <addison@yahoo-inc.com> Thu, 02 August 2007 15:20 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 1IGcTl-0008NB-4v; Thu, 02 Aug 2007 11:20:45 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IGcTj-0008Mz-Jc for ltru-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 11:20:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGcTh-0008Mr-Tn for ltru@ietf.org; Thu, 02 Aug 2007 11:20:43 -0400
Received: from rsmtp2.corp.yahoo.com ([207.126.228.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGcTg-0002ej-IS for ltru@ietf.org; Thu, 02 Aug 2007 11:20:41 -0400
Received: from [10.72.77.193] (snvvpn2-10-72-77-c193.corp.yahoo.com [10.72.77.193]) (authenticated bits=0) by rsmtp2.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l72FKUOC058150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Aug 2007 08:20:31 -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=qoesp0lUs+qJ0vctqSYg8Os4QuH5TucCXjjnB1BM2aK2tlP9R8x/gPyboUIMthph
Message-ID: <46B1F63D.6080002@yahoo-inc.com>
Date: Thu, 02 Aug 2007 08:20:29 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: John Cowan <cowan@ccil.org>
Subject: Re: [Ltru] UTF-8 in which field? (Was: draft-ietf-ltru-4646bis-07
References: <46AF5B86.3010207@yahoo-inc.com> <20070802072141.GA15254@nic.fr> <20070802125433.GA11786@mercury.ccil.org>
In-Reply-To: <20070802125433.GA11786@mercury.ccil.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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

John Cowan wrote:
>>
>> The 'Description' field MAY thus include UTF-8 characters.
> 
> The point is that "ASCII" is both an encoding and a repertoire,
> whereas "UTF-8" is only an encoding.  The meaning is that the
> Description field may contain characters that are not in the
> ASCII repertoire (whereas most other fields must not).  The
> whole file is in the UTF-8 encoding.
> 

+1

If "non-ASCII" isn't sufficiently positive, a proper reformulation would be:

--
The 'Description' field MAY include the full range of Unicode 
characters. At least one of the 'Description' fields MUST be written or 
transcribed into the Latin script; additional 'Description' fields MAY 
also include a description in a non-Latin script.
--

Note that this reverses the existing order. The current text says:

--
At least one of the 'Description' fields MUST be written or transcribed 
into the Latin script; additional 'Description' fields MAY also include 
a description in a non-Latin script. The 'Description' field MAY thus 
include non-ASCII characters.
--

Addison

-- 
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