- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Nov 2022 09:49:09 +0000
- To: public-css-archive@w3.org
> "installed fonts referenced directly by family name, rather than via @font-face rules, are considered to have a unicode-range that covers the entire Unicode code space".
This feels like a good solution to me - until this discussion I'd assumed that's how it worked anyway.
I don't think we should check if the local font has U+0020 actually defined. We explicitly don't do this for web-fonts, it would be inconsistent to require it for local fonts. If for any reason this behaviour needs customising it can be done so with
`@font-face { font-family: "Arial"; src: local(Arial); unicode-range: nnn; }`
--
GitHub Notification of comment by faceless2
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4796#issuecomment-1305352190 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 November 2022 09:49:11 UTC