How about adding UN/LOCODE in zone.tab?

[Paul Koning]

On Feb 4, 2011, at 4:00 PM, Guy Harris wrote:

> 
> On Feb 4, 2011, at 8:35 AM, Ian Abbott wrote:
> 
>> Including LOCODE in zone.tab may or may not be a good idea, but I'm
>> trying hard to think why you'd want to encode a time zone in a language tag.
> 
> If by "with a language tag" he means that en-US-u-tz-usnyc" is a language tag, yes, that's bogus.
> 
> If, however, he means that "en-US-u-tz-usnyc" is a locale tag, which includes a language tag but can include more information as well, that makes sense.  Unfortunately, RFC 6067 calls it a "language tag", which is a bogus term for anything that specifies time zones, collating orders, and other information that has nothing to do with language.

At the risk of going off topic for this list, collating order certainly is (largely) a language question.  Not entirely; some languages may have a choice of several collating orders based on national or cultural differences.

I do agree that timezone is in no way a language related thing.

	paul