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 16987 - i18n-ISSUE-131: UTF-32 BOMs
Summary: i18n-ISSUE-131: UTF-32 BOMs
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-07 18:24 UTC by Addison Phillips
Modified: 2012-05-08 16:08 UTC (History)
5 users (show)

See Also:


Attachments

Description Addison Phillips 2012-05-07 18:24:23 UTC
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?
Comment 1 Ian 'Hixie' Hickson 2012-05-08 00:29:29 UTC
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."