W3C home > Mailing lists > Public > www-style@w3.org > January 2014

[css-ruby] Should `ruby-merge' initial value be `auto'?

From: kawabata taichi <kawabata.taichi@gmail.com>
Date: Sat, 25 Jan 2014 02:47:23 +0900
Message-ID: <CA+PRW9-FeGutpVHWOe5JCtHWxx9TbTt2pD1g77wh1y=EKoa-Qg@mail.gmail.com>
To: "www-style@w3.org" <www-style@w3.org>
Dear people concerned with CSS-Ruby,

Currently, CSS Ruby `ruby-merge` property's initial value is
`separate`.(http://www.w3.org/TR/css3-ruby/#collapsed-ruby). I would
prefer that this initial value be `auto` instead of 'separate'.

Rationale: Multiple <rb> tag within single <ruby> tag is typically
used for compound words (Jukugo). For Jukugo, the best rendering
algorithm is "Jukugo-Ruby algorithm", as its name says (see JLREQ
3.3.7). By specifying `auto` by default, the rendering engine would
display the ruby text by the best algorithm it supports (including
Jukugo-Ruby algorithm).

The current initial value, 'separate', is typically suitable if multiple
<rb>s do not constitute a compound word. In such a case, an author would
put them in different ruby segments, thus this spec is a bit
unnatural.

As of it, I would like to propose to change the initial value of
`ruby-merge' to be 'auto' instead of 'separate'.

Regards

*
http://www.w3.org/TR/jlreq/#positioning_of_jukugoruby_with_respect_to_base_characters


-- 
---------------------------------------------------------------------
KAWABATA, Taichi E-mail: kawabata.taichi@gmail.com
Received on Friday, 24 January 2014 17:47:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:18 UTC