- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Mar 2021 21:38:19 +0000
- To: public-css-archive@w3.org
> But I understand this is based on browser/server tech, and you wouldn't need to repackage your fonts. Is that correct? The [Range Request](https://www.w3.org/TR/2020/NOTE-PFE-evaluation-20201015/#range-request) method requires the font be re-ordered for optimal performance: > the font must be pre-processed to move glyph outlines to the end of the file, and to ensure that the outlines are independent The [Patch Subset](https://www.w3.org/TR/2020/NOTE-PFE-evaluation-20201015/#patch-subset) method uses a standard, unprocessed font for the first request. The `supports` part is saying that subsequent requests will download binary patches to the first font, and that the client and server will be communicating which glyphs are needed and which are already downloaded. So Range Request requires some ahead of time preprocessing, but can be served by a standard HTTP server; the Patch Subset method requires an active server extension and, in general, gives [better to much better](https://www.w3.org/TR/2020/NOTE-PFE-evaluation-20201015/#conclusions) performance. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6063#issuecomment-790078185 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 March 2021 21:38:20 UTC