W3C home > Mailing lists > Public > www-font@w3.org > April to June 2010

RE: Chrome to support WOFF

From: Sergey Malkin <sergeym@microsoft.com>
Date: Sat, 24 Apr 2010 22:27:41 +0000
To: John Daggett <jdaggett@mozilla.com>, Thomas Phinney <tphinney@cal.berkeley.edu>
CC: "www-font@w3.org" <www-font@w3.org>, Chris Lilley <chris@w3.org>
Message-ID: <E39A28CD8A7CE44CA0BDEE6269E8B0A556441185@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
John Daggett wrote:

> The Chromium code does the extra step of reconstructing the entire 
> font, sanitizing a specific set of tables and omitting all others 
> (including GSUB, GPOS, and GDEF currently).  

Wouldn't removing OpenType layout table break all international fonts?
Also, modification of original font file (even automatically by application) may be incompatible with some font licenses, isn't it?

> This was done because of concerns about potential security 
> bugs lurking in platform font API's, especially on Windows. 

Do you think that font processing code in Windows is so insecure that it justifies crippling font functionality? 

Received on Saturday, 24 April 2010 22:28:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:34 UTC