This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15340 - Separate ISO-8859-1 from windows-1252 even if the mapping table is the same because of "misinterpreting for compatibility"
Summary: Separate ISO-8859-1 from windows-1252 even if the mapping table is the same b...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-26 11:20 UTC by Masatoshi Kimura
Modified: 2012-10-30 17:13 UTC (History)
1 user (show)

See Also:

Attachments

Description Masatoshi Kimura 2011-12-26 11:20:50 UTC 
Per HTML(5| Living) Standard, "misinterpreting for compatibility" is one of parse errors [1] [2].
It's impossible for User-Agents (especially conformance checkers) to report the parse error if ISO encodings are mere aliases of Windows encodings.
As a side note, Opera is the only browser which treats ISO-8859-1 as an alias of windows-1252.

[1] http://dev.w3.org/html5/spec/Overview.html#preprocessing-the-input-stream
[2] http://www.whatwg.org/specs/web-apps/current-work/#preprocessing-the-input-stream
Comment 1 Anne 2012-04-08 11:58:25 UTC 
I think conformance checkers should flag non-utf-8 usage regardless, as it's problematic with URLs, <form> submission, etc.