W3C home > Mailing lists > Public > www-international@w3.org > January to March 2010

Re: Ruby in HTML5

From: Suzumizaki-Kimikata <szmml@h12u.com>
Date: Thu, 11 Mar 2010 09:30:11 +0900
To: MURAKAMI Shinyu <murakami@antenna.co.jp>
Cc: Jeroen Ruigrok van der Werven <asmodai@in-nomine.org>, Richard Ishida <ishida@w3.org>, www-international@w3.org, public-html-ig-jp@w3.org
Message-Id: <20100311093011.cae6e8a6.szmml@h12u.com>
I think nesting ruby-element causes logically unsuitable.

Ruby-text(<rt>) will always annotate ruby-base even the rt is
second one, and never annotate the pair of ruby-base and the other
ruby-text.

Correct:
Ruby-base is annotated by ruby-text-1, and
Ruby-base is annotated by ruby-text-2.

At least logically Wrong:
Ruby-base is annotated by ruby-text-1, and
the pair of ruby-base and ruby-text-1 is annotated by rt-2.

-- 
Suzumizaki-Kimitaka <szmml@h12u.com>
JPN: 鈴見咲 君高

On Wed, 10 Mar 2010 22:06:30 +0900
MURAKAMI Shinyu <murakami@antenna.co.jp> wrote:

> I'm not sure whether HTML5 should adopt the XHTML complex ruby,
> but I think the both sides ruby is possible with current HTML5.
> 
> Ruby use cases from the JLReq document
> http://www.w3.org/International/datespace/2010/02/jlreq-examples/
> shows the example "[8] Figure 117: Ruby on both sides" as:
> 
> 1. XHTML complex.
>  <ruby>
>    <rbc><rb>東</rb><rb>南</rb></rbc><rtc><rt>とう</rt><rt>なん</rt></rtc>
>    <rtc><rt rbspan="2">たつみ</rt></rtc>
>  </ruby>
> 
> and says "There is no way to do this using HTML5 markup."
> 
> I think it's possible because HTML5 doesn't prohibit nesting ruby.
> 
>   <ruby class="after">
>     <ruby>東<rt>とう</rt>南<rt>なん</rt></ruby>
>     <rt>たつみ</rt>
>   </ruby>
> 
> with stylesheet:
>   ruby       { ruby-position: before }
>   ruby.after { ruby-position: after }
> 
> This seems simpler than the XHTML complex markup.
> 
> -- 
> 村上 真雄 (MURAKAMI Shinyu)
> http://twitter.com/MurakamiShinyu
> Antenna House Formatter:
> http://www.antenna.co.jp/AHF/
Received on Thursday, 11 March 2010 00:30:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 11 March 2010 00:30:49 GMT