W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

RE: I expect all foundries to start offering web font licenses within 6 months.

From: Richard Fink <rfink@readableweb.com>
Date: Sun, 19 Jul 2009 21:15:57 -0400
To: "'Sylvain Galineau'" <sylvaing@microsoft.com>, 'Håkon Wium Lie' <howcome@opera.com>
Cc: "'Dave Crossland'" <dave@lab6.com>, "'Thomas Phinney'" <tphinney@cal.berkeley.edu>, "'www-font'" <www-font@w3.org>
Message-ID: <004201ca08d7$a658d1b0$f30a7510$@com>
Sunday, July 19, 2009 <sylvaing@microsoft.com
>Correction and clarification: Hakon is right, WEFT itself does still
require this input.

I don't think so. Check again. WEFT's interface is weird and can mislead.
I've created EOT's simply by specifying a domain name. No scanning of web
pages required. You can also list drive letters and folders on the local
system in case you're creating a Hyper-Text Application or similar app,
also.

On the other hand, in WEFT's defense, the scanning feature can be useful,
there are circumstances where one would want to finely subset for a
particular page.

Cheers,

Rich

-----Original Message-----
From: Sylvain Galineau [mailto:sylvaing@microsoft.com] 
Sent: Sunday, July 19, 2009 8:38 PM
To: Håkon Wium Lie; rfink@readableweb.com
Cc: 'Dave Crossland'; 'Thomas Phinney'; 'www-font'
Subject: RE: I expect all foundries to start offering web font licenses
within 6 months.

Correction and clarification: Hakon is right, WEFT itself does still require
this input. But EOT in general does not require fonts to be
subsetted. While this certainly seems an unnecessary limitation today, I
don't think it was in the past and have yet to see any feedback
data demonstrating that this was the main issue.

Note that since the format has been documented, others have been writing
tools to convert TTFs to EOT. See
http://edward.oconnor.cx/2009/07/how-to-create-eot-files-without-microsoft-w
eft for instance.

(Not endorsing this tool, just noting its existence).

>-----Original Message-----
>From: Sylvain Galineau
>Sent: Sunday, July 19, 2009 5:27 PM
>To: 'Håkon Wium Lie'; rfink@readableweb.com
>Cc: 'Dave Crossland'; 'Thomas Phinney'; 'www-font'
>Subject: RE: I expect all foundries to start offering web font licenses
>within 6 months.
>
>>Using WEFT, authors had to scan their HTML pages to create EOT files.
>>This was highly inconvenient and proably the major reason why nobody
>>used it. You're saying that the solutions in development will be even
>>more inconvenient?
>
>This is, to my knowledge, untrue. You would do that if you wanted to
>generate an EOT file that was subsetted for
>a static page. There is no need to do this if all you want to do is set
>up a font file for your whole site.
>
>
Received on Monday, 20 July 2009 01:16:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:02 GMT