- From: <bugzilla@jessica.w3.org>
- Date: Sat, 13 Jul 2013 10:47:09 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22661 Bug ID: 22661 Summary: Meaning of raw UTF-16LE/BE Classification: Unclassified Product: WHATWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: HTML Assignee: ian@hixie.ch Reporter: silviapfeiffer1@gmail.com QA Contact: contributor@whatwg.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org, robin@w3.org, www-international@w3.org Depends on: 20089 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 +++ http://dev.w3.org/html5/spec/infrastructure.html#a-utf-16-encoding 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. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Saturday, 13 July 2013 10:47:11 UTC