Re: [HTML5 Ruby] <Segmentation & Categorization> Step 13 really necessary?

Dear Robin,

Sample something like this?

1. Ruby on Ruby text

<ruby>
   <rb>出発</rb>
   <rp>（</rp>
   <rt><ruby><rb>たびだち</rb><rt>depature</rt></ruby></rt>
   <rp>) </rp>
</ruby>

2. Ruby on Ruby base

  <ruby>
    <ruby><rb>東南</rb><rt>とうなん</rt></ruby>
    <rt>たつみ</rt>
</ruby>

2nd case is appeared in old double-sided ruby use case
(e.g. http://www.w3.org/International/notes/ruby-extension/).

1st case may be useful for historical document where annotations
tends to be complex.

Regards,



On Tue, Mar 18, 2014 at 11:10 PM, Robin Berjon <robin@w3.org> wrote:

> Hi,
>
>
> On 18/03/2014 12:01 , kawabata taichi wrote:
>
>> The Step 13 of [1] (13. If root has a ruby element ancestor, then abort
>> these steps.) prohibits the the processing of nested ruby.
>>
>> However, nested ruby feature is already implemented in Chrome and
>> Safari, and it is likely that someone in the world may already use it.
>> Also, it is unclear that what would be the expected result of
>> "aborting" the process.
>>
>> As of it, I think that Step 13 of [1] may be no longer necessary, and
>> would like to propose to remove the step 13 from the specification.
>>
>
> I would be happy to remove step 13. However, I am curious about the
> support you mention in Chrome and Safari, can you please point me to a test
> showing that in practice?
>
> Thanks!
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>



-- 
---------------------------------------------------------------------
川幡 太一 (KAWABATA, Taichi) E-mail: kawabata.taichi@gmail.com