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

Addison Phillips <> Sun, 08 July 2007 15:04 UTC

Return-path: <>
Received: from [] ( by with esmtp (Exim 4.43) id 1I7YIu-0001RT-Hc; Sun, 08 Jul 2007 11:04:04 -0400
Received: from ltru by with local (Exim 4.43) id 1I7YIs-0001RI-On for; Sun, 08 Jul 2007 11:04:02 -0400
Received: from [] ( by with esmtp (Exim 4.43) id 1I7YIs-0001R0-EM for; Sun, 08 Jul 2007 11:04:02 -0400
Received: from ([]) by with esmtp (Exim 4.43) id 1I7YIo-0006N1-3I for; Sun, 08 Jul 2007 11:04:02 -0400
Received: from [] ( []) (authenticated bits=0) by (8.13.8/8.13.6/y.rout) with ESMTP id l68F3Vxd024906 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Jul 2007 08:03:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; s=serpent;; 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=yMEoc2I3pHoL45vSVBg4gYDqOIIOpBKscLZi17sD0iB8yu27Ay2k1cVAMxtwCAp7
Message-ID: <>
Date: Sun, 08 Jul 2007 08:03:29 -0700
From: Addison Phillips <>
User-Agent: Thunderbird (Windows/20070604)
MIME-Version: 1.0
To: Doug Ewell <>
Subject: Re: [Ltru] Re: Solving the UTF-8 problem
References: <007401c7c0c4$74d1ad90$6401a8c0@DGBP7M81> <> <008701c7c106$31f2d1b0$6401a8c0@DGBP7M81>
In-Reply-To: <008701c7c106$31f2d1b0$6401a8c0@DGBP7M81>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: LTRU Working Group <>
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

 > Will people have the patience to wait a few days before going ahead and
 > using the beta as if it were official?  If they don't, that eliminates
 > the whole benefit of having a beta.

The only fields that can contain non-ASCII characters are Description 
and Comment fields. Neither has a stability guarantee and neither is 
normative. A data encoding error, furthermore, would probably cause 
implementation failures rather than lead to enshrinement of mojibake.

A beta period for the registry is critical for stabilized fields. 
However, I note that IANA wouldn't ever change a record sent by the LSR 
(we require whole records to be sent) and we introduced a "beta-period" 
for the final record in 4646bis. An additional beta for the registry 
seems like gilding the lily.


Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.

Ltru mailing list