- From: Nat McCully via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2023 22:40:23 +0000
- To: public-css-archive@w3.org
> I think we should ask Nat McCully and Masataka Hattori if the problem is still worth solving. (My intuition is that it is.) Yes, it definitely is worth solving so each app didn't have to do its own solution, perhaps also relying on certain fonts' implementations (or influencing them with a particular hack behavior). I suspect something lacking in the font data, as well, unless we agree on a foolproof method of determining uprightness in vertical that is cheap, and then further agree on conventions for when things switch axes. My assumption is always that the lowest level expects Latin horizontal behaviors, and requires a no-op (i.e. no difference in code) when rendering Latin text in any direction. Thus all the special-casing happens with Japanese in vertical, with rotation upright and x- and y-axis-reversal, change of slant (see above -- actually the slant is not just a shear from the Roman baseline but rather a shear, scale, and rotate all about the glyph center), uneven scaling, other distortions, etc. All this could be codified in the font data better, and make other improvements for vertical text that acknowledge the mix of orientation when mixing scripts (even in the same font). -- GitHub Notification of comment by macnmm Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4044#issuecomment-1726633888 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 September 2023 22:40:24 UTC