W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2011

Re: Update to Language Tags article about extension subtags

From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
Date: Tue, 08 Feb 2011 20:09:36 +0900
Message-ID: <4D512470.9010803@it.aoyama.ac.jp>
To: Richard Ishida <ishida@w3.org>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Sorry, an earlier message should have gone to a different thread.

Anyway, while I'm at it, a few comments:

 >If you feel you really need to use these tags, you should read the 
specification, rather than this article.

tags -> subtags

 >Extension and private use tags are introduced by a single letter tag,

tags -> subtags

 >or 'singleton'. The singleton for extensions is defined by the 
organization that registers it.

No, the singleton is defined in the registry. It's totally possible 
(although not important enough to mention in the article) that somebody 
proposes an -f- extension, but gets told s/he has to take a -b- extension.

 >The singleton for private use is x. Any subtags after the singleton 
can only be 8 characters in length, however you are allowed to use 
multiple subtags.

"Any subtags after" -> "Like any subtags, subtags after" (to make clear 
this is a general rule)

 >Extension subtags allow for extensions to the language tag. For 
example, the extension subtag u has been registered by the Unicode 
Consortium to add information about language or locale behaviour. Many 
locale identifiers require additional "tailorings" or options for 
specific values within a language, culture, region, or other variation. 
This extension provides a mechanism for using these additional 
tailorings within language tags for general interchange.

 >For example, the following indicates that phonebook collation order 
should be used by an application:

"that phonebook collation order should be used by an application": Not 
only that, but also e.g. that sorted data in a document is sorted 
according to this collation, and so on.

 >The subtags that follow the u- extension and their meanings are 
defined by RFC 6067 and by the Unicode Consortium in the Common Locale 
Data Repository (CLDR). They are not defined by BCP 47.

I'd say "The u- extension is defined in RFC 6067, which points to the 
Unicode Consortium in the Common Locale Data Repository (CLDR) for 
details on the subtags that follow it." And I'd add a reference/link to 
the exact document for this.

 >Private-use subtags do not appear in the subtag registry, and are 
chosen and maintained by private agreement amongst parties.

Change "choosen and maintained by" to something like "may be used by"

 >Private use tags should be used with great care, and avoided whenever 
possible, since they interfere with the interoperability that RFC 5646 
exists to promote.

"since they interfere with the interoperability" sounds quite abstract 
given the level of the rest of the document. I'd say something like 
"since their meaning isn't clearly defined" or some such.

 >The following example of a private use tag

tag -> subtag

 >may identify a specific type of US English, but only within a closed 
community. Outside of that private agreement, its meaning cannot be 
relied upon.

I'd avoid the word "community" at all for private stuff. It's not wrong 
in absolute terms, but it's too inviting and thus giving the wrong 


Regards,    Martin.

On 2011/02/08 5:07, Richard Ishida wrote:
> Chaps,
> See the proposed text at
> http://www.w3.org/International/articles/language-tags/temp.php#extension
> Please send me any comments before I make the changes live.
> Addison, I suggest we discuss this on Wednesday with a view to blessing
> it, if all is ok.
> Thanks,
> RI

#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp
Received on Tuesday, 8 February 2011 11:10:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:07 UTC