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

Re: Feedback for rb from html5j.org (was RE: HTML5 and ruby

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Sun, 22 Jan 2012 13:40:24 +0100
To: Koji Ishii <kojiishi@gluesoft.co.jp>
Cc: Richard Ishida <ishida@w3.org>, CJK discussion (public-i18n-cjk@w3.org) <public-i18n-cjk@w3.org>
Message-ID: <20120122134024833859.3dc4f444@xn--mlform-iua.no>
From: Richard Ishida [mailto:ishida@w3.org]
> Here are some key questions:

> 2. do we need rb and rtc for complex ruby support, or is it 
> sufficient to rely on a mixture
> of recursive ruby markup plus a second <rt> element (depending on 
> the use case)?

Regarding complex ruby, then in order to use <rtc> cross browser -  in 
IE9, Firefox 9 and Safari 5 - the following mark-up is necessary:

<ruby>
   <rbc>
      <rb>foo</rb>
   </rbc>
   <rtc>
      <!--[if !ie]>--><ruby><!--<![endif]-->
      <rp>(</rp>
      <rt>bar</rt>
      <rp>)</rp>
   </rtc>
</ruby>

Explanation: Placing <ruby> inside cause IE9 to close the current 
<ruby> element. Whereas in Firefox and Webkit, then the <rtc> is closed 
as soon as the parser sees an <rp> or <rt> element.

I don't know how IE10 reacts - that woudl be interesting to hear. But 
the above shows that currently, then XHTML 1.1 Ruby does not work cross 
browser.
-- 
Leif Halvard Silli
Received on Sunday, 22 January 2012 12:41:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 January 2012 12:41:07 GMT