W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > July to September 2012

[Bug 17967] Parsing algorithm should not preclude Complex Ruby

From: <bugzilla@jessica.w3.org>
Date: Fri, 20 Jul 2012 15:37:37 +0000
Message-Id: <E1SsFGr-0002yF-E2@jessica.w3.org>
To: public-i18n-cjk@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17967

--- Comment #2 from fantasai <fantasai.bugs@inkedblade.net> 2012-07-20 15:37:36 UTC ---
This bug is very specifically about the parser, and about HTML's
forwards-compatibility in the case that a future version defines complex ruby
to be in scope. It's not about whether or not to support complex ruby; that's a
separate debate, where several approaches are being discussed and there isn't a
clear conclusion yet. I'd rather not complicate this bug by discussing
approaches to ruby, please let it suffice to say that at some point in the next
20 years it's entirely possible for it (or some subset of it) to be in scope
and the current parsing algorithm has no benefits over one that is more
forwards-compatible.

-- 
Configure bugmail: https://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 Friday, 20 July 2012 15:37:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 20 July 2012 15:37:41 GMT