[Bug 14709] lang tag validation is insufficiently specified

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14709

--- Comment #6 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-11-07 17:42:23 UTC ---
(In reply to comment #4)
> (In reply to comment #1)
> > Another way to look at this problem is "should ISO 639-3 (three-letter) codes
> > be allowed when the BCP47 tag for a given language is the two-letter ISO 639-1
> > code?"
> 
> Since BCP47 says:
> 
> 2.2.8.  Grandfathered and Redundant Registrations
> 
>    Prior to RFC 4646, whole language tags were registered according to
>    the rules in RFC 1766 and/or RFC 3066.  All of these registered tags
>    remain valid as language tags.
> 
> and since RFC1766 allows both 2 and 3 letter primary language tags but doesn't
> require shortest use, the restriction you propose above would effectively
> subset BCP47, which is undesirable, and could reduce interoperability.

I don't know know precisely what John D. had in mind, but I spot no
'subsetting' of BCP47 anywhere. Grandfathered tags are valid language tags.

So, it is for instance not so that 'mya' was every allowed according to the old
rules. 'Mya' has never been a valid language tag for use inside @lang and
@xml:lang.

What you quoted only means that in the *hyphothetical* situation that 'mya' had
been registered, then it would have remained a valid tag, despite the fact that
it could not have been registered according *todays* rules.

Thus I don't see that you have brought forward a valid reason to not do what
John D proposed.

PS: All the language official tags are found here:
http://www.iana.org/assignments/language-subtag-registry

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 7 November 2011 17:42:27 UTC