IETF Logo Mail Archive

Re: [Ltru] Re: extlang

Addison Phillips <addison@yahoo-inc.com> Tue, 19 June 2007 21:34 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 1I0lLN-0003kL-U6; Tue, 19 Jun 2007 17:34:33 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I0lLM-0003kA-Qi for ltru-confirm+ok@megatron.ietf.org; Tue, 19 Jun 2007 17:34:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0lLM-0003jP-Go for ltru@ietf.org; Tue, 19 Jun 2007 17:34:32 -0400
Received: from rsmtp1.corp.yahoo.com ([207.126.228.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0lLK-0001SJ-5g for ltru@ietf.org; Tue, 19 Jun 2007 17:34:32 -0400
Received: from [172.21.37.80] (duringperson-lx.corp.yahoo.com [172.21.37.80]) (authenticated bits=0) by rsmtp1.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l5JLYPXD096162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jun 2007 14:34:26 -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=dwVEZsncBqd0jQ+DWO9XUfgJE6MJtZP2Vy4eNxOGBcojEatTVJDnwpeD91eWuCjS
Message-ID: <46784BE1.7000205@yahoo-inc.com>
Date: Tue, 19 Jun 2007 14:34:25 -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] Re: extlang
References: <30b660a20706171252l3c61d451p464b96e864d1a515@mail.gmail.com><007f01c7b166$8ef7bf10$6401a8c0@DGBP7M81><30b660a20706181006x3efbf772t9a0751feb070a6cb@mail.gmail.com><20070619013433.GA15048@mercury.ccil.org><003701c7b238$16124fc0$6401a8c0@DGBP7M81><20070619140547.GB30227@mercury.ccil.org><4677F589.3090003@yahoo-inc.com><20070619205855.GA19853@sources.org><46784742.9080009@yahoo-inc.com> <20070619212227.GF12168@mercury.ccil.org> <000d01c7b2b8$dc7aa420$6601a8c0@oemcomputer>
In-Reply-To: <000d01c7b2b8$dc7aa420$6601a8c0@oemcomputer>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
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

Randy Presuhn wrote:
> ...
>> Also 639-3 languages that aren't encompassed now but become so in
>> future.
> ...
> 
> If there is a real expectation that this will happen, this
> will be critical to the extlang discussion, due to the
> implications for stability in encoding.
> 

Yes, although I think we dealt with that: the encoding is stable and the 
newly enclosed language remains a primary language. Such an eventuality 
would be supremely icky.

There was also a proposal (I think I made it) to limit extlangs to "at 
4646bis birth only"---that is, only currently enclosed languages that 
are otherwise unencoded would be extlangs. This gets us the (for 
example) the enclosed Chinese dialects (etc.), but not any future 
extlangs. Future registrations would be primary language subtags only.

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

v2.23.0 | Report a Bug | By Email