[Bug 13113] Parsing algorithm should not preclude Complex Ruby

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13113

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |NEEDSINFO

--- Comment #13 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-04 06:57:21 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: Did Not Understand Request
Change Description: no spec change
Rationale: I still haven't seen data on this. Make a random selection of books,
magazines, web pages, or whatever, and tabulate how many of each kind of ruby
these texts have, ideally with examples of each for my own education. It's
possible that what's in the spec is insufficient, but I am highly skeptical
that the level of complexity being proposed is necessary to solve read-world
use cases.

-- 
Configure bugmail: http://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 Thursday, 4 August 2011 06:57:23 UTC