- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 09:45:22 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10890
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |WONTFIX
--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-12 09:45:22 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: This case is made illegal because "here be dragons": specifying
<meta charset=utf-16> actually has either no effect, or is actually explicitly
interpreted as UTF-8. In no case does it have the effect it appears to have,
namely to declare the encoding as being UTF-16. Therefore we would not be doing
anyone in favours by allowing it.
--
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.
You reported the bug.
Received on Tuesday, 12 October 2010 09:45:24 UTC