W3C home > Mailing lists > Public > public-html@w3.org > October 2012

[Bug 19214] New: i18n-ISSUE-195: No further ruby element descendants

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Oct 2012 16:29:20 +0000
To: public-html@w3.org
Message-ID: <bug-19214-2495@http.www.w3.org/Bugs/Public/>

           Summary: i18n-ISSUE-195: No further ruby element descendants
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
        AssignedTo: erika.doyle@microsoft.com
        ReportedBy: www-international@w3.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, www-international@w3.org

(endorsed by the i18n WG)

4.6.20 The ruby element

"A single ruby element, but with no further ruby element descendants"

Does this mean that you can't have a ruby element and additional characters
alongside it? For example, since multiple annotations don't always refer to the
same sequences of characters, it would be important to ensure you could do the


This should result in the rendered text where the hiragana is mono-ruby
pronunciation that refers only to the first kanji character, and the katakana
is group-ruby that refers to the kanji+hiragana base characters together.

I think that it is clear how this should be parsed, but it must be allowed by
the rules in the spec.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 2 October 2012 16:29:24 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:28 UTC