- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Oct 2020 07:03:58 +0000
- To: public-css-archive@w3.org
Web fonts are the only sure way for a web author to use these less-supported languages. Naming a specific font and hoping the user has it installed is less likely to work than using web fonts. There’s a trade-off here. International support is clearly important, but privacy is also definitely important. Different UA’s policies have different implications for different users. I chose the word “may” here on purpose, simply to describe the trade-off. There are many different points on the spectrum between blocking fonts for privacy and allowing fonts for internationalization, and all of those points have reasonable arguments for them, based on the specific considerations of the UA and their users. The sentence “User Agents may choose to ignore User-Installed Fonts” is *true* (de facto). We shouldn’t remove it from the spec. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5421#issuecomment-705375452 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 October 2020 07:04:00 UTC