- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 09:22:15 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10811
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-12 09:22:15 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:
As far as I can tell this requirement makes as much sense as requiring that
characters in the string be rendered so that they are recognisably similar to
the glyphs that Unicode shows, or that text should be rendered with glyphs next
to each other rather than on top of each other.
Unicode defines the semantics of these characters. If the browsers don't honour
them, then that's a violation of Unicode's semantics. I don't see what that has
to do with HTML. Adding a requirement to follow the requirements in Unicode
doesn't make any difference to whether the requirements will be followed or
not.
--
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:22:17 UTC