- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Jul 2022 11:01:18 +0000
- To: public-css-archive@w3.org
I agree with @jfkthame and @dbaron that we don't want a fragile situation where the `unicode-range` is sometimes ignored, and that gets depended on. Consider some old font which has ₠ where it should have €, we would want a `unicode-range` that excludes U+20AC Euro sign (because that font has the wrong glyph) to always be honoured, right? And (to get back to installed _vs._ webfonts) that includes an `@font-face` with `unicode-range` where the `src` uses `local()`. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7449#issuecomment-1172879520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 2 July 2022 11:01:20 UTC