- From: Fuqiao Xue via GitHub <noreply@w3.org>
- Date: Wed, 18 Mar 2026 02:35:52 +0000
- To: public-css-archive@w3.org
> Neither https://www.w3.org/TR/clreq/ nor css-ruby is super clear as to whether that kind of layout is also expected for horizontal bopomofo ruby. https://www.w3.org/TR/clreq/#positioning_of_zhuyin mentions horizontal writing mode in many places. I'm not sure which specific parts you found unclear. We can certainly make some improvements. > what the behavior actually is. CLREQ gives a good starting point for the happy path where everything is set up properly, but what if there's more than the max 3 characters + 1 tone mark that it expects? What if some aren't the same font-size? what if there's some non-bopommofo in there as well? What about… I can discuss this issue with the Chinese Layout Task Force. > But as far as I can tell, fonts don't handle this currently (neither the placing of the tone mark, nor the spacing between the letters), so it may well be fully up to the css layout engine to handle this. There are some discussions related to font implementation. You can check them out here: https://github.com/w3c/clreq/issues/241 > One extra question: is the layout logic described in CLREQ The One True layout logic used everywhere, or is that a simplified or compromise solution synthetized by the i18n group? I am asking not because I have any reason not to follow it, but because multiple sources (if they exist) could be informative about error case / corner case handling. As I understand it, the content within clreq largely describes ideal typographic scenarios. In practice, you may encounter layouts that deviate from these guidelines. However, this does not necessarily imply that the behavior in clreq is incorrect. If you want further reference materials, we would be happy to look some up. -- GitHub Notification of comment by xfq Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13533#issuecomment-4079227602 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 March 2026 02:35:53 UTC