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

"Debbie Garside" <> Fri, 08 July 2011 21:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D62DE21F8A5A for <>; Fri, 8 Jul 2011 14:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jrd1r9aX9LxG for <>; Fri, 8 Jul 2011 14:47:23 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 081E321F8A66 for <>; Fri, 8 Jul 2011 14:47:17 -0700 (PDT)
Received: from ICTPC ([]) by with MailEnable ESMTP; Fri, 08 Jul 2011 22:47:20 +0100
From: "Debbie Garside" <>
To: "'John Cowan'" <>
References: <> <090501cc3da0$354aad90$9fe008b0$> <>
In-Reply-To: <>
Date: Fri, 8 Jul 2011 22:48:48 +0100
Message-ID: <090a01cc3db8$d542e6b0$7fc8b410$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acw9okUWrXqwtgb7Rd6ZRwhJZoUMEgAFnMDg
Content-Language: en-gb
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 21:47:23 -0000

Thanks John.  That makes sense.

Best wishes


-----Original Message-----
From: John Cowan [] On Behalf Of John Cowan
Sent: 08 July 2011 20:05
To: Debbie Garside
Cc: 'Doug Ewell';
Subject: Re: [Ltru] draft-davis-t-langtag-ext

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