16987 2012-05-07 18:24:23 +0000 i18n-ISSUE-131: UTF-32 BOMs 2012-05-08 16:08:29 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WONTFIX P2 minor --- 1 addison ian ian mike public-html-admin public-html-wg-issue-tracking public-i18n-core public-html-bugzilla oldest_to_newest 67425 0 addison 2012-05-07 18:24:23 +0000 4.3.1 The script element http://www.w3.org/TR/html5/scripting-1.html#the-script-element Step 15, down around 1. The list of BOM sequences doesn't include the UTF-32 BOMs. While UTF-32 is explicitly unsupported by HTML5, it might be a good idea to list the BOM's as unsupported? 67454 1 ian 2012-05-08 00:29:29 +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: Rejected Change Description: no spec change Rationale: The spec already says "Authors should not use UTF-32, as the encoding detection algorithms described in this specification intentionally do not distinguish it from UTF-16."