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 10971 - Polyglot publication should be more careful about UTF-16, UTF-16BE and UTF-16LE
Summary: Polyglot publication should be more careful about UTF-16, UTF-16BE and UTF-16LE
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML/XHTML Compat. Authoring Guide (ed: Eliot Graff) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-04 11:46 UTC by Henri Sivonen
Modified: 2010-10-07 12:38 UTC (History)
5 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-10-04 11:46:45 UTC 
The polyglot publication repeats what was bug 10258 in the HTML5 spec itself.

UTF-16BE and UTF-16LE are registered encodings that are by definition BOMless, so the spec should say "big-endian UTF-16" and "little-endian UTF-16" instead.
Comment 1 Eliot Graff 2010-10-05 22:55:32 UTC 
Hi Henri.

Can you clarify something for me? Are you merely asking that I replace "UTF-16BE" with "big-endian UTF-16" as well as replacing "UTF-16LE" with "little-endian UTF-16"? Or is there more to this than that?

Thanks.
Comment 2 Henri Sivonen 2010-10-06 07:54:39 UTC 
(In reply to comment #1)
> Hi Henri.
> 
> Can you clarify something for me? Are you merely asking that I replace
> "UTF-16BE" with "big-endian UTF-16" as well as replacing "UTF-16LE" with
> "little-endian UTF-16"?

Yes.

> Or is there more to this than that?

No, that's it.
Comment 3 Eliot Graff 2010-10-06 19:19:51 UTC 
This change is in the Editor's Draft dated 6 October.

Thank you.
Comment 4 Henri Sivonen 2010-10-07 12:38:10 UTC 
Thanks.