- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Mar 2025 09:39:56 +0000
- To: public-css-archive@w3.org
An alternative approach, rather than filtering or constraining to a set of vanilla OS system fonts: Run the browser with its own font environment - In ChromeOS and Android we use a set of open-source fonts, a collection of fonts from the set of [Noto fonts](https://fonts.google.com/noto) and others from the open-source set of Google fonts as the font environment. Create a font environment based on these existing corpuses for the browser independent of the system fonts and update this with the browser. Serve font matching and fallback requests from this set of fonts. If done right, in my understanding this would then lead to very little entropy being gained from this font environment, probably not much other than: "this is browser x, version y". It has challenges in terms of distribution - the font environment, decompressed is probably around 200-400MB depending on locale support. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11775#issuecomment-2713362488 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 March 2025 09:39:56 UTC