- From: Liam Quin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jan 2021 11:03:18 +0000
- To: public-css-archive@w3.org
On Thu, 2021-01-21 at 01:09 -0800, Mike Bremford wrote: > `font-weight: 400, "Helvetica" "Arial" 500, "Times" 300;` This is starting to look like CORS headers, which are notoriously difficult to get right. > I'm also wondering about some of these [...] You can for sure add font-variant (if there's a small caps font in which lower case letters render as small caps, convert to lower case and use it, otherwise if the OpenType small caps are available, use htem, otherwise convert to all caps), and font-features, where stylistic set 1 might do something entirely unacceptable in Arial compared to Helveica. Of course, i might prefer to say "use the first font family that has a roman and an italic with small caps for the roman and support for the historical ligatures feature" which is massively more useful than tryingto do it backwards based on a list of font names, especially when there are 57 varieties of Helvetica and i'd want different letter spacing depending on which one is used, but CSS doesn't expose the font foundry or font version. -- Liam Quin, https://www.delightfulcomputing.com/ Available for XML/Document/Information Architecture/XSLT/ XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org -- GitHub Notification of comment by liamquin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/126#issuecomment-764556968 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 11:03:50 UTC