- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Thu, 23 Feb 2012 03:29:43 +0100
- To: public-i18n-cjk@w3.org
On 02/23/2012 03:02 AM, Roland Steiner wrote: > On Thu, Feb 23, 2012 at 07:24, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no <mailto:xn--mlform-iua@xn--mlform-iua.no>> > wrote: > > > 2. Do we agree that column-major - what is in HTML5 now - should be > > non-conforming? > > > I don't think that's an option as it would break existing pages. A solution > should have graceful fallback to both the current standard as well as to no > <ruby> support. Agreed. HTML5 ruby, as it stands now, can be folded into a either a row-major model or a column-major model, so aside from the parsing algorithm (Bug 13113), it does not create a conflict with moving forward on a row-major model. It just means that in a row-major model, the HTML5 markup is only capable of producing group ruby, not jukugo ruby. But a row-major model can easily be a superset of what's in HTML5 today. http://www.w3.org/Bugs/Public/show_bug.cgi?id=13113 (in which hsivonen asks for parsing algorithm changes that would make HTML5 future-compatible with row-major ruby markup) ~fantasai
Received on Thursday, 23 February 2012 02:30:15 UTC