W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2011

[Bug 10830] i18n comment : Please add support for rb

From: <bugzilla@jessica.w3.org>
Date: Thu, 08 Dec 2011 10:31:56 +0000
To: public-i18n-core@w3.org
Message-Id: <E1RYbGe-0004dD-TJ@jessica.w3.org>

Richard Ishida <ishida@w3.org> changed:

           What    |Removed                     |Added
                 CC|                            |ishida@w3.org

--- Comment #75 from Richard Ishida <ishida@w3.org> 2011-12-08 10:31:55 UTC ---
Here's a (rather belated) summary of what came out of the discussion 
between the i18n WG and Ian at TPAC.

Ian had not realised that we wanted rb to be only an optional tag. This 
initially made some difference to his amenability to consider it's use. 
We, on the other hand, realised that we hadn't properly thought through 
whether you could achieve ruby styling using span (which will be allowed 
inside ruby in html5).

We discussed the legacy question, but found it hard to argue for rb 
solely on that ground, since other things have been discontinued in 
html, and certainly we agreed that the html5 model is easier to use, in 
general, than the old model (because it reduces the markup overhead for 
the content author).  The question is whether we need rb for particular 
use cases.

Ian was open to hear technical arguments for retaining rb. Much of the 
discussion at that time centred around the possible need for rb to 
support complex ruby. We reviewed the use cases for complex ruby with 
Ian, but we believe that we don't yet have a clear answer as to whether 
rb is required in order to achieve the goals of complex ruby (ie. ruby 
on both sides, and association of rt with rb). We agreed that we needed 
to investigate that (which will entail better understanding how we could 
achieve the effects of complex ruby in html5) and the pros and cons of 
using span, and put our findings to Ian. (see comment 59).

Since then we have realised that there may be some other use cases, such 
as replacement of ruby base text with ruby text, or aggregation of ruby 
texts within parens for jukugo ruby, that we overlooked in our discussion.

Note that the WG, during our discussion, didn't come to Ian's conclusion 
in comment 67 that "<rb> was in fact not only unnecessary, but 
potentially harmful", but we did feel that we needed to do further 
research into the pros and cons for the use of rb. As Ian also says in 
comment 67, "Richard took an action item to discuss this further with 
other members of the working group and report back". We have begun this 
process, and are hoping to continue along that route without having to 
resort to the adversarial jousting competition that escalation often 

To that end, we would like to consolidate the various technical 
arguments put forward for rb, ensure that they are investigated more 
thoroughly where needed, and more clearly draw out the pros and cons for 
its use.

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 Thursday, 8 December 2011 10:32:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:07 UTC