- From: Chris Lilley <chris@w3.org>
- Date: Wed, 21 May 2014 04:17:10 +0200
- To: "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotype.com>
- CC: "w3c-webfonts-wg (public-webfonts-wg@w3.org)" <public-webfonts-wg@w3.org>
Hello Vladimir, Wednesday, May 21, 2014, 12:33:06 AM, you wrote: > One issue that was discussed recently at the MPEG font list about > DSIG is the reliance of some of the Windows applications on DSIG > presence to distinguish OT fonts from TTF, and by extension, to use > this distinction to enable the OpenType layout features. Wow, that is a really broken heuristic! > It is not > clear whether only certain applications are affected, or any that > use the underlying Win API, but this is something we may need to > investigate because of the WOFF2 spec recommendation to remove DSIG > because it will be compromised by pre-processing and reconstruction > steps. What we may consider instead (or in addition to) is to remove > the DSIG table while encoding a font and recreate a dummy DSIG (if > the original font had it) to preserve font compatibility with Win > API. That is a) gross and b) will be removed again by the font validators that are commonly used to check downloaded fonts. > Let’s give it a time to discuss it at the next telcon (on May 28). > > > > Thank you, > > Vlad > > > -- Best regards, Chris mailto:chris@w3.org
Received on Wednesday, 21 May 2014 02:17:13 UTC