10257 2010-07-29 07:18:52 +0000 Meta charset sniffing need to resolve aliases before checking UTF-16ness 2010-12-01 15:30:24 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All VERIFIED INVALID https://bugzilla.mozilla.org/show_bug.cgi?id=582788 P2 normal --- 1 hsivonen ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37157 0 hsivonen 2010-07-29 07:18:52 +0000 Step 12 says "If charset is a UTF-16 encoding, change the value of charset to UTF-8." It should resolve charset to the canonical name first, and if that's UTF-16, UTF-16BE or UTF-16LE (what about 32?), change charset to UTF-8? 37160 1 hsivonen 2010-07-29 07:31:29 +0000 Actually, Safari allows iso-10646 to sniff to the default instead of UTF-8. So maybe this bug report is wrong. 37162 2 hsivonen 2010-07-29 11:36:19 +0000 Thanks to Philip, I've examined four Web pages that declare iso-10646 in meta. (Thankfully, they are rare.) 3 were ASCII. One was Windows-1252. So from this data, it seems we should *not* do alias resolution before the UTF-16 to UTF-8 aliasing step. 37163 3 hsivonen 2010-07-29 12:05:16 +0000 (In reply to comment #1) > Actually, Safari allows iso-10646 to sniff to the default instead of UTF-8. So > maybe this bug report is wrong. Chances are I'm misreading Safari's encoding menu.