Rated 5 out of 5 stars

To whom it may concern:

According to w3 css3 standards information on Ruby found here http://www.w3.org/TR/css3-ruby/

It mentioned that bopomofo ruby should be handled correctly if below CSS is used.

ruby.bopomofo { writing-mode: tb-rl }

So far none of the browsers or addons that supports RUBY accomplishes this. It would be nice if HTML ruby achieves this. Though besides the standard bopomofo, I also would like to see the Taiwanese holo portion of bopomofo also implemented. the bopomo for Taiwanese holo is already implemented in unicode standard.

http://www.unicode.org/charts/collation/chart_Bopomofo.html

The real issue with rendering bopomofo in right verticle mode is the placement of the tonal marks, as seen in the w3 css3 standard page. There are 4 tonal marks in bopomofo for mandarin chinese, however for Taiwanese holo and hakka, there are 2 more tonal marks. So the 6 complete tonal marks that should be treated correctly are below

ˊ ˇ ˋ ˙ ˪ ꜕

ˊ U+02CA
ˇ U+02C7
ˋ U+02CB
˙ U+02D9
˪ U+02EA
꜕ U+A715 (or is it ˫ U+02EB doesn't matter, make both of them a tonal mark for bopomofo)

I have no idea why these are in the same unicode page with the rest of the bopomofo, but so far that's how it is.

All but one of these tonal marks should be placed on the right hand side of the vertical Ruby text, like the example in the w3 css3 page. which woud look something like below.


ㄧˋ


The one exception is ˙ U+02D9, which would be placed above the rest of the ruby text, which would look something like this.

˙




Currently the only application that processes this correctly is Microsoft Words. If you have Asian Language package with your MS Words, and put in 爸吧, high light these two characters and goto "Format -> Asian Layout -> Phonetic Guides", in the setting window make sure the alignment is set to "Right vertical" mode, and you could see the different between˙ U+02D9, and the rest of the tonal marks.

I know this is asking a lot, bit it is part of the w3 css3 standard. If HTML Ruby can be the first to support this, it would be great news.

This review is for a previous version of the add-on (5.13.2).