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 7215 - character encodings and XML
Summary: character encodings and XML
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE, NoReply
Depends on:
Reported: 2009-08-05 10:07 UTC by Anne
Modified: 2010-10-04 13:58 UTC (History)
3 users (show)

See Also:


Description Anne 2009-08-05 10:07:33 UTC
Should the character encoding not only apply to HTML? This is how it was originally. Now it is in its standalone section that bit of information seems to have gone lost.
Comment 1 Ian 'Hixie' Hickson 2009-08-08 01:17:26 UTC
Could you elaborate?
Comment 2 Anne 2009-08-08 07:16:18 UTC
The text in "Character encodings" was initially part of the HTML parsing section. It is no longer there and the new section and text seems to implicate that ISO-8859-1 must be treated as Windows-1252 in XML too. And while I personally would be fine with that, so far we've always said this was text/html-only.
Comment 3 Maciej Stachowiak 2010-03-14 14:48:45 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.