Re: [csswg-drafts] [css-ruby] Alignment of bopomofo

@r12a:

> Not sure how you came to your conclusion here.

I believe that when I wrote "Bopomofo is only used for single characters…", I was referring to single *base* characters.

I think the point I was trying to make (last year) was that the default doesn't matter much because (A) a UA stylesheet can address the issue with CSS4 Selectors support and (B) there will normally be a negligible difference between `space-between` and `center`—with the biggest difference applying to the allocation of space of a two‐character bopomofo annotation applied to a single base character—unless the base character is unusually large.

I don't feel strongly about this issue though. I think I was mostly interested in chiming in because I saw “`ruby:lang(zh)`” proposed, which I think is the wrong approach since it lacks a script string (i.e., `bopo`) in the language selector. (See one of my preceding posts for a CSS approach that I felt was better.)

> I suggest reading https://r12a.github.io/scripts/bopomofo/ontheweb

This was an interesting read. I'd suggest changing the text color from gray to a more legible black though to encourage more people to read it. (I manually changed the text color.)

For what it’s worth, I think a better approach to handling bopomofo tone mark rendering would be to create `bopomofo-corner-tone-offset`, `bopomofo-dot-position`, and `bopomofo-word-separator` CSS properties. Bopomofo isn't intrinsically tied to ruby as seen at http://dict.revised.moe.edu.tw/cgi-bin/cbdic/gsweb.cgi?o=dcbdic&searchid=Z00000153482, where bopomofo appears as tabular data, or at http://stroke-order.learningweb.moe.edu.tw/bopomofo.do, where bopomofo `input` element text field values cannot be marked with markup.

-- 
GitHub Notification of comment by patrickdark
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1907#issuecomment-425289248 using your GitHub account

Received on Friday, 28 September 2018 01:13:10 UTC