15340 2011-12-26 11:20:50 +0000 Separate ISO-8859-1 from windows-1252 even if the mapping table is the same because of "misinterpreting for compatibility" 2012-10-30 17:13:16 +0000 1 1 1 Unclassified WHATWG Encoding unspecified All All RESOLVED WONTFIX P2 normal Unsorted 1 VYV03354 annevk mike sideshowbarker+encodingspec oldest_to_newest 62029 0 VYV03354 2011-12-26 11:20:50 +0000 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 66507 1 annevk 2012-04-08 11:58:25 +0000 I think conformance checkers should flag non-utf-8 usage regardless, as it's problematic with URLs, <form> submission, etc.