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 22661 - Meaning of raw UTF-16LE/BE
Summary: Meaning of raw UTF-16LE/BE
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Depends on: 20089
  Show dependency treegraph
Reported: 2013-07-13 10:47 UTC by Silvia Pfeiffer
Modified: 2013-07-23 23:16 UTC (History)
7 users (show)

See Also:


Description Silvia Pfeiffer 2013-07-13 10:47:09 UTC
Those terms are not defined in the referenced RFC and I don't follow what you mean't by them. Could you clarify? Thanks.

+++ This bug was initially created as a clone of Bug #20089 +++ says:

"The term a UTF-16 encoding refers to any variant of UTF-16: self-describing UTF-16 with a BOM, ambiguous UTF-16 without a BOM, raw UTF-16LE, and raw UTF-16BE. [RFC2781]"

What is 'raw' UTF-16LE/LE ?  Presumably, it's 'ambiguous UTF-16' without a BOM but with an encoding declaration in the transport layer? 

Actually 'self-describing' is not completely unambiguous either. 

Please clarify what these words mean.
Comment 1 Anne 2013-07-13 12:21:57 UTC
We shouldn't need these terms given the Encoding Standard which we reference already. Seems confusing to also reference something else for utf-16.
Comment 2 contributor 2013-07-23 23:16:48 UTC
Checked in as WHATWG revision r8081.
Check-in comment: Closer integration with