- From: <bugzilla@jessica.w3.org>
- Date: Tue, 23 Aug 2011 00:05:35 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13786
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-23 00:05:35 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, 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:
http://dev.w3.org/html5/decision-policy/decision-policy.html
Status: Rejected
Change Description: no spec change
Rationale: The problem is that a number of servers actually send charset=""
parameters, so we have to support it. We can't ignore it because if the
character encoding is set to something else then we would be corrupting the
data if we interpreted it as UTF-8. (What if one day we all move on to some new
encoding scheme? It's important that we be able to migrate. We can't easily do
so if we are ignoring charset=""!)
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 23 August 2011 00:05:37 UTC