- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Mar 2024 08:22:51 +0000
- To: public-css-archive@w3.org
We could replace "equivalent" by "corresponding", to make the sentence more accurate. Given the following sentence in the spec, I think this is a reasonable feature though: > It has no effect on the underlying content, and must not affect the content of a plain text copy & paste operation. We could expand on that and say something like: > […] must not affect the content of a plain text copy & paste operation<ins>, nor speech synthesis</ins>. I'm not sure which OTF feature you're refering to. https://learn.microsoft.com/en-us/typography/opentype/spec/features_pt#tag-ruby maybe? If so, it could do that, but typically is more related with stroke thickness, so that the ruby font size and the main font size relate well to each other. Regardless, OTF features are font dependent, and this is not, so there are different tradeoffs, and I think it's fine to have both. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10140#issuecomment-2019797930 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 March 2024 08:22:52 UTC