W3C home > Mailing lists > Public > www-font@w3.org > October to December 2009

RE: Next step?

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Thu, 22 Oct 2009 20:43:37 +0000
To: Tal Leming <tal@typesupply.com>
CC: www-font <www-font@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E0236B44F@TK5EX14MBXC120.redmond.corp.microsoft.com>
> From: Tal Leming [mailto:tal@typesupply.com]
> Sent: Thursday, October 22, 2009 11:35 AM

<snip>

> To be clear, I am not endorsing CWT and I am not speaking as a co-
> author of the WOFF specification. I am speaking as someone who works
> with a number of foundries to produce fonts and as someone who
> actually experimented with EOTL. Font makers already have enough
> undefined expectations and bugs to guess about and work around. I
> quite strongly do not want to have more of these. It's bad for
> everyone involved -- the OS/app makers, the font makers and, most
> importantly, the users.

Yes, a formal CWT spec must define what a font generator (font vendor, tool)
must do in order to generate a font file that will work in IE and any browser
that implements the spec.  
Received on Thursday, 22 October 2009 20:44:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 October 2009 20:44:14 GMT