Re: Hosted source format?

John -

The current specification allows for some dynamic subsetting but is focused on pre-computed files. Therefore the typical files on the client side would be "initial" subsetted font files (which would generally be in WOFF2 format with a couple of added tables) and patches (which are their own format but typically compressed with brotli).

Skef
________________________________
From: John Hudson <john@tiro.ca>
Sent: Thursday, July 11, 2024 9:03 AM
To: 3668 FONT <public-webfonts-wg@w3.org>
Subject: Hosted source format?


EXTERNAL: Use caution when clicking on links or opening attachments.


Message ID: <w3c/IFT/pull/190@github.com>

Congratulations, all, on the working draft publication. I am encouraging colleagues to take the time to familiarise themselves with the technology and also to check whether the wording of their webfont license agreements might need any updates to accommodate it.

This reminds me of a query I had for Garret during the TPAC meeting in Vancouver. At that time, he presumed the hosted source format for IFT would be an uncompressed TTF or OTF file, but I pointed out that license agreements might be worded in such a way that webfonts need to be hosted as WOFF2 or WOFF. Garret thought it should be possible for the hosted source font to be pre-compressed as WOFF2 or WOFF, then decompressed, subsetted, and recompressed as WOFF2 for delivery. I wanted to check on the status of this query, and wasn’t able to find a definite answer in the working draft text.

JH


--

John Hudson
Tiro Typeworks Ltd    www.tiro.com<http://www.tiro.com/>

Tiro Typeworks is physically located on islands
in the Salish Sea, on the traditional territory
of the Snuneymuxw and Penelakut First Nations.

__________

EMAIL HOUR
In the interests of productivity, I am only dealing
with email towards the end of the day, typically
between 4PM and 5PM. If you need to contact me more
urgently, please use other means.