Re: [Ltru] draft-davis-t-langtag-ext

John Cowan <> Fri, 08 July 2011 19:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D3F8C21F8B99 for <>; Fri, 8 Jul 2011 12:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id owxmLr3Te4OU for <>; Fri, 8 Jul 2011 12:05:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2A8B621F8B75 for <>; Fri, 8 Jul 2011 12:05:28 -0700 (PDT)
Received: from cowan by with local (Exim 4.69) (envelope-from <>) id 1QfGMe-0000Vn-Mp; Fri, 08 Jul 2011 15:05:24 -0400
Date: Fri, 8 Jul 2011 15:05:24 -0400
From: John Cowan <>
To: Debbie Garside <>
Message-ID: <>
References: <> <090501cc3da0$354aad90$9fe008b0$>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <090501cc3da0$354aad90$9fe008b0$>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: John Cowan <>
Cc:, 'Doug Ewell' <>
Subject: Re: [Ltru] draft-davis-t-langtag-ext
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 08 Jul 2011 19:05:28 -0000

Debbie Garside scripsit:

> (Being lazy here) Does BCP47 reference the -u extension RFC?

No, it doesn't.  It provides for the existence of a
registry of extension subtags, which IANA maintains at .

> If not things seem to be getting very messy with subtag rules
> potentially in a number of RFCs.

Inevitably so.  BCP 47 is based on the primary-language, region, script,
variant model of language tagging, but it was foreseen that other models
might need to be incorporated into it.  BCP points to the extension
registry, which points to the RFCs documenting those extensions.  It
also explains how to strip the extensions if you don't want them.

> Just as an aside, ISO are actually merging all of the ISO 639
> standards into one workable document.  It will be known as ISO 639 and
> will replace all the other standards.  I am the new Editor (appointed
> in Korea in June).


Not to perambulate                 John Cowan <>
    the corridors        
during the hours of repose
    in the boots of ascension.       --Sign in Austrian ski-resort hotel