[mpeg-OTspec] Proposed update of the 'head' table flags

[Thomas Phinney]

Speaking wearing my font developer hat for a moment, if leaving out DSIGs
breaks things in current MS apps I would not stop including DSIGs for some
years to come. Even after new versions stop depending on it....

Yes, it was weird to require an unverified DSIG. But we shouldn't punish
users for an MS decision.




On Wed, May 14, 2014 at 4:53 PM, Ken Lunde lunde at adobe.com [mpeg-OTspec] <
mpeg-OTspec at yahoogroups.com> wrote:

>
>
> Thomas,
>
>
> You wrote:
>
> > What would it mean to deprecate the current DSIG, exactly? Would we be
> telling people not to put it in fonts? Or telling consumers not to rely on
> it being present, or not to rely on it being meaningful, or...?
>
> All of the above, I think. ;-)
>
> There are fonts out there with valid DSIG tables, and some with "stub"
> (empty) ones. Given the persistence of fonts, updating fonts to remove the
> DSIG table would be an ordeal (and a half). Going forward, font developers
> should not include DSIG tables, but part of that message needs to be
> coupled with Microsoft changing their products to not depend on the
> presence of the DSIG table.
>
> It sounds like a "baby steps" approach to deprecation will be necessary.
>
> I think that for font developers, the current practice of production
> should continue until the infrastructure no longer depends on the DSIG
> table.
>
> Microsoft then has work to do. :-)
>
> -- Ken
>
>  
>



-- 
On paper books and ebooks: “Paper books are the packaging that books come in
.”
—Cory Doctorow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20140514/84cea754/attachment.html>