This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25952 - Handling more than 2 ruby annotation containers at commiting a ruby segment.
Summary: Handling more than 2 ruby annotation containers at commiting a ruby segment.
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-03 02:39 UTC by tkawabat
Modified: 2014-06-04 14:56 UTC (History)
4 users (show)

See Also:


Attachments

Description tkawabat 2014-06-03 02:39:59 UTC
In Step 5 of [1], the statement says:

> Create a new ruby segment. It is described by a list of bases set to
> current bases, a base DOM range set to current bases range, and a
> first and second ruby annotation containers that are respectively the
> first and second items of the current annotation containers list.
> Append this new ruby segment at the end of ruby segments.

This states that only "a first and second ruby annotations" are put
to current annotation containers list. However, I think this
restriction is reminiscent of old restriction that ruby annotation
containers are limited to two. As there is no longer a restriction on
number of ruby containers in a single ruby segment, I think this
"first and second" restriction should be removed.

[1] ...
http://www.w3.org/html/wg/drafts/html/CR/text-level-semantics.html#commit-a-ruby-segment
Comment 1 Robin Berjon 2014-06-04 14:56:34 UTC
I agree with your assessment and have rephrased to take into account the fact that it's an arbitrary list.