W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > January to March 2012

Re: Arguments against HTML double-sided ruby (was: Re: Memo from ruby disucssion with Roland)

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 24 Feb 2012 02:26:49 +0100
To: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
Cc: "public-i18n-cjk@w3.org" <public-i18n-cjk@w3.org>, KOBAYASHI Tatsuo(FAMILY Given) <tlk@kobysh.com>
Message-ID: <20120224022649975426.3d217426@xn--mlform-iua.no>
MURATA Makoto, Fri, 24 Feb 2012 07:47:59 +0900:
> I am wondering why there have been no reactions to my mail.  Or,
> do people discuss about double-sided ruby only for justifying optional
> rb elements rather than committing to HTML double-sided ruby?

Rather than assuming that a good bye to double sided ruby can permit 
that we drop <rb>, I would suggest to first define the requirements for 
single ruby. And thereafter to check whether the outcome of the single 
ruby case, has anything to say with regard to how simple it would be to 
support double sided ruby.

For single sided ruby, the choice of row-major coding style versus 
column-major coding style will decide: In single-sided column-major 
coding style, then <rb> is not strictly necessary. But in the more 
<table> element inspired single-sided row-major coding style, then <rb> 
seems necessary in order to associate ruby texts with specific base 

The advantages of row-major coding style is fallback, searching, 
accessibility and stuff like that. Since ruby is meant to benefit users 
and not only be a visual extra, it seems logical to give high priority 
to these issues.

> Note that double-sided ruby "is also very rare.",  according to JLRec.
Leif Halvard Silli
Received on Friday, 24 February 2012 01:27:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:59:17 UTC