W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2011

[Bug 14709] lang tag validation is insufficiently specified

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 Nov 2011 00:58:15 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RNDXT-00031p-LV@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14709

--- Comment #3 from John Daggett <jdaggett@mozilla.com> 2011-11-07 00:58:14 UTC ---
(In reply to comment #2)
> If I read you correctly, you want HTML5 to explicitly forbid that
> "mya" is treated like a synonym for "my". And this might make sense.

Exactly.  There are others arguing that internal API's should be treated
as "services", thus allowing pass-thru of language subtags that are not
BCP47 language subtags, like 'mya' which is an ISO 639-3 tag but not a
BCP47 one.

> When it comes to CSS, then it is clear that it is not synonymous -
> just consider that  div:lang(mya){} would not select <div lang="my">.
> But when it comes to screenreaders and OpenType APIs etc, then this
> might not be as clear.

Right.  The same might be true if a user agent used an API for
hyphenation data that took full language names (e.g. 'Burmese'). One
interpretation of the wording in the current spec would be that user
agents should permit lang="Burmese" to match a lookup of Burmese
hyphenation data even though the language is technically "unknown".

-- 
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 01:00:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 November 2011 01:00:22 GMT