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 9128 - It seems a bad idea to willfully violate the character model specification for a new standard. New HTML documents should have the correct encoding and should not need to be mis-interpreted. Why not specify mandatory UTF-8 anyway?
Summary: It seems a bad idea to willfully violate the character model specification fo...
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-23 14:18 UTC by contributor
Modified: 2010-10-04 14:48 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-02-23 14:18:07 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#character-encodings-0

Comment:
It seems a bad idea to willfully violate the character model specification for
a new standard. New HTML documents should have the correct encoding and should
not need to be mis-interpreted. Why not specify mandatory UTF-8 anyway?

Posted from: 131.111.69.235
Comment 1 Ms2ger 2010-02-25 18:17:51 UTC 
Because the willful violation is there for legacy content, rather than for new content.