- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jan 2024 08:09:04 +0000
- To: public-css-archive@w3.org
> We didn't discuss chws/vchw specifically, but they don't seem appropriate because for text-spacing we want the browser deciding which characters get trimmed, not the font. I'd agree with that. The fact that this feature uses context detection at the font level means that it'll fail when there are multiple fonts (or multiple font-sizes…). Also, [the documentation for that feature](https://learn.microsoft.com/en-us/typography/opentype/spec/features_ae#chws) does say this: > Application interface: If a layout engine supports advanced layout for CJK text as described in [CLREQ](https://www.w3.org/TR/clreq/), [JLREQ](https://www.w3.org/TR/jlreq/) or [KLREQ](https://www.w3.org/TR/klreq/), this feature should not be used. An engine with support for `text-spacing` is exactly that, that's one more point in the direction of not using this feature. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8293#issuecomment-1882583510 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 January 2024 08:09:07 UTC