- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Sep 2010 16:44:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10661
Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xn--mlform-iua@xn--mlform-i
| |ua.no
--- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2010-09-21 16:44:40 ---
(In reply to comment #4)
> (FWIW, I think using private use language subtags in public is questionable,
> but if software fails to ignore unrecognized subtags and fails to pay attention
> to the standard subtags (en and US), that's a bigger problem that needs to go
> in the appropriate bug databases.)
Where is it defined that user agents must ignore the 'x-*' part? I don't think
that anyone can infer what 'en-us-x-hixie' means. There is no semantic
difference between 'en-us-x-hixie' and 'en-us-x-myscript' or
'en-us-x-my-invented-orthogra-phy'. It would perhaps be smart of user agents to
- by default - ignore the '-x-whatever' part. But I don't think it is said
anywhere that they should.
> Is this a practical problem? That is, are there screen readers in use that
> don't properly ignore language subtags they don't know about. If there are,
> have you filed bugs against those screen readers about implementing RFC 5646
> properly?
First one needs to know what the proper treatment of such tags is. From BCP47:
]]
2.2. Language Subtag Sources and Interpretation
…
o The single-letter subtag 'x' introduces a sequence of private use
subtags. The interpretation of any private use subtag is defined
…
solely by private agreement and is not defined by the rules in
this section or in any standard or registry defined in this
document.
[[
--
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 Tuesday, 21 September 2010 16:44:43 UTC