Re: WOFF and extended metadata

Kernest is currently not including any metadata in the WOFF files it serves. Partially because I knew the structure of the XML was influx and partially because it's not required for the fonts to render.

-----------------------
Garrick Van Buren
612 325 9110
garrick@kernest.com
-----------------------
Kernest.com
Free, Subscription, and Web Native fonts.
-----------------------

On Jun 9, 2010, at 4:11 PM, Christopher Slye wrote:

> 
> On Jun 8, 2010, at 11:45 PM, Sylvain Galineau wrote:
> 
>> I have asked for examples of usage of this format with real fonts.
>> Nothing. All I get is assertions that it exists and it might therefore
>> not be worth anyone's time to provide me with that data. I've never 
>> before been on a WG where asking for real-life use-cases seems such a 
>> burden. It does not inspire confidence.
> 
> I'll attempt to collect some examples of foundries building and licensing WOFF fonts. I think that's the first concern, right? Foundries that are creating persistent WOFF files that might cause compatibility issues later.
> 
> Of course various entities are also dynamically generating transient WOFF and it would be interesting to know what metadata they are attaching, if any. Vlad, is Monotype serving WOFF in its web fonts service, and if so, are you putting any metadata in there?
> 
> I'll write to Typekit and ask them. (Or they can answer here if they're watching.)  -Christopher

Received on Wednesday, 9 June 2010 21:37:41 UTC