- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Jun 2023 14:15:14 +0000
- To: public-css-archive@w3.org
Maybe it's the name of the property that is the stumbling-block here, to some extent. Would it be better if it were called `font-typographic-convention`? The initial value would be `auto`, meaning to use behavior implied by the content language (or any other available clues), but it would also allowing an explicit choice of an OpenType "language system" tag (specified as a string). A request for a non-`auto` typographic convention could be treated as an input to the font-matching algorithm, causing the UA to explicitly look for a font that supports the requested rendering. (This could of course equally well be done with `font-language-override`, though we haven't heard any call for this, afaik. The assumption has generally been that an author wanting this level of control would use it in conjunction with a specific webfont.) -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5484#issuecomment-1585682453 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 10 June 2023 14:15:16 UTC