Closed
Bug 285463
Opened 20 years ago
Closed 20 years ago
different language tags for the same language should be considered equivalent
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
INVALID
People
(Reporter: annevk, Assigned: dbaron)
Details
(Keywords: css2, testcase)
Attachments
(1 file)
|
287 bytes,
text/html
|
Details |
See: <http://www.loc.gov/standards/iso639-2/englangn.html#two> Simple CSS testcase coming up to prove we do otherwise. I guess we need some kind of mapping table and normalize all the values to a sensible default for comparison. (This might be the wrong component by the way since it also affects the HTTP language headers. They might need separate bugs.)
| Reporter | ||
Comment 1•20 years ago
|
||
| Assignee | ||
Updated•20 years ago
|
Severity: normal → minor
Comment 2•20 years ago
|
||
Personally I think this is WONTFIX. Three-letter codes equivalent to existing two-letter codes are invalid according to both RFC 3066 (http://www.ietf.org/rfc/rfc3066.txt) and the current draft of its successor (http://www.ietf.org/internet-drafts/draft-phillips-langtags-10.txt). I think that the criteria for what we should support are the RFCs and the IANA registry, rather than ISO 639.
| Reporter | ||
Comment 3•20 years ago
|
||
From the RFC:
> When a language has both an ISO 639-1 2-character code and an ISO
> 639-2 3-character code, you MUST use the tag derived from the ISO
> 639-1 2-character code.
So this is INVALID.Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•