- From: <bugzilla@jessica.w3.org>
- Date: Sat, 28 Jan 2012 21:57:34 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15195
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-01-28 21:57:34 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: You're the first person to raise this in two and a bit years. If we
get one comment every two years from people who don't understand the
requirements in Unicode and UTF-16, I'm pretty sure we can explain the
situation as I did above without any difficulty. Adding additional text to the
spec for something like this does not help the majority of readers, who either
don't care about this particular topic, or understand it well enough that the
warning satisfies their instinctive reaction of pointing out the conflict with
Unicode.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 28 January 2012 21:57:36 UTC