10258 2010-07-29 07:22:15 +0000 Spec should be more careful about UTF-16, UTF-16BE and UTF-16LE 2010-10-04 14:28:34 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED P2 normal --- 1 hsivonen ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37158 0 hsivonen 2010-07-29 07:22:15 +0000 The BOM sniffing tables say the encoding is UTF-16BE or LE. Those are by definition BOMless, so the spec should say big-endian UTF-16 and little-endian UTF-16. In various places, the are checks if the encoding of something is UTF-16. Those checks should probably also check for UTF-16BE and UTF-16LE. 37491 1 ian 2010-08-16 21:38:31 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's pedantic comments. 37492 2 contributor 2010-08-16 21:39:11 +0000 Checked in as WHATWG revision r5301. Check-in comment: UTF-16 terminology. http://html5.org/tools/web-apps-tracker?from=5300&to=5301