- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jan 2021 14:25:30 +0000
- To: public-css-archive@w3.org
> Personally, I'm not keen on the more complex forms being suggested for properties like font-weight, letter-spacing, etc., with lists of specific per-family values to be applied. It feels to me like it would become quite cumbersome and hard to maintain. I agree with that. Jonathan, I think @xiaochengh, @chrishtr and I were talking about a similar approach to what you were drafting when talking about the ascent-overrides, etc. - One thing we talked about were potential issues with how specific the from-to mapping is if only using a font family name: In your example, would `base-family: Times;` refer to a web font, a system font, or both? In some cases, common system font families like Times are sometimes not available on a system and then mapped to other fonts, like Tinos, or for Arial, mapped to Deja Vu Sans on Linux for example. So it's a bit tricky to uniquely identify the intended base. One idea I had was to use something like `base: local(<PostScript or full font name>)` in that case, but that would not work for web fonts. Alternatively, some kind of link-id could be used. (Also, only very raw ideas so far). -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/126#issuecomment-764677512 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 January 2021 14:25:32 UTC