[MPEG-OTSPEC] Introducing breaking changes into the spec (was: RE: [EXTERNAL] Proposal to deprecate derived search values)

[Peter Constable]

Of course: if there’s to be a new font format, we’d want it to be one that works everywhere.

But that would inevitably take some time.

If a site owner replaces all of the “Selawik Regular” OT/WOFF usage on their site with “Selawik New Regular” in NewFont Format (or whatever), and do so when there isn’t broad browser support and without any compat for older browers to use the older font, then that would be breaking the site for many uses. But it’s not the new font that broke things; it’s the decisions of the site owner.


Peter

From: Dave Crossland <dcrossland at google.com>
Sent: Friday, September 11, 2020 3:30 PM
To: Peter Constable <pgcon6 at msn.com>
Cc: Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com>; mpeg-otspec <mpeg-otspec at lists.aau.at>
Subject: Re: [MPEG-OTSPEC] Introducing breaking changes into the spec (was: RE: [EXTERNAL] Proposal to deprecate derived search values)


On Fri, Sep 11, 2020, 6:25 PM Peter Constable <pgcon6 at msn.com<mailto:pgcon6 at msn.com>> wrote:
If I tried to use a Metafont format file as a Web font and nothing worked, would that be considered a “breaking change”? I don’t think so. It’s just a not-well-supported scenario.
This is where branding matters, I think. "OT2" or "OFF2" seems bound to be expected to work in a way "Novel Format Name" (like METAFONT, which most font users don't know) would not.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200911/a490ea4e/attachment.html>