DSIG

[Simon Daniels MSFT]

As mentioned DSIG is currently the defined way to differentiate between an OpenType font and a TrueType font, and some apps use the presence of the table to treat the font differently than a regular TrueType font. By definition all OpenType CFF fonts are OpenType, so DSIG isn’t needed.




Any proposal to deprecate DSIG would need to come up with a bullet proof mechanism to differentiate between TrueType and OpenType, and not break app behavior, or user expectations - eg. how would a customer react if a font identified as OpenType today, became a TrueType font tomorrow if the new spec defined OpenType as being a font that includes GSUB or GPOS? What would we then call an OpenType CFF font that didn’t include GPOS or GSU?



Regardless I would be interested in seeing a proposal written up. 




Cheers, Si
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20140516/371f96e0/attachment.html>