[MPEG-OTSPEC] checksum / 4-byte table offset weasel wording
Peter Constable
pgcon6 at msn.com
Mon Aug 31 22:14:29 CEST 2020
Agreed on how to approach deprecations.
To start incorporating a data generation/authoring versus parsing distinction systematically across the spec would be a non-trivial undertaking. I think it would be best to open issues on specific parts of the text where there isn't sufficient clarity in this regard, and be flexible on the language used to make the appropriate distinctions in each context.
Peter
-----Original Message-----
From: mpeg-otspec <mpeg-otspec-bounces at lists.aau.at> On Behalf Of Norbert Lindenberg
Sent: Monday, August 31, 2020 1:05 PM
Cc: MPEG OT Spec list (mpeg-otspec at lists.aau.at) <mpeg-otspec at lists.aau.at>
Subject: Re: [MPEG-OTSPEC] checksum / 4-byte table offset weasel wording
“Software implementations / applications” is not precise enough – font producers are also software implementations / applications. “Font consumers” is fairly broad too – ttx and CoreText consume fonts in very different ways –, but it’s a meaningful subset of software.
We also need “font producers” separately from the data format. When deprecating features, we need to keep the description of the deprecated data around so that consumers can correctly interpret old fonts, but we have to instruct font producers what to produce instead.
Best regards,
Norbert
Lindenberg Software LLC
> On Aug 31, 2020, at 10:08, Peter Constable <pgcon6 at msn.com> wrote:
>
> I generally like the idea of clearly distinguishing between producer and consumer, though I think the distinction can be described in terms of requirements/recommendations for font data versus software implementations / applications.
> From: Simon Cozens <simon at simon-cozens.org>
>
> This is another example where it's useful to have the distinction between what font consumers should do and what font producers should do.
_______________________________________________
mpeg-otspec mailing list
mpeg-otspec at lists.aau.at
https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.aau.at%2Fmailman%2Flistinfo%2Fmpeg-otspec&data=02%7C01%7C%7C731c879ee59d4b4ae74108d84de93867%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637345011350058088&sdata=R3rlXDpvzRwv9Gl9pxTcc6VnY8QlAceyMBxIY4Yb5YU%3D&reserved=0
More information about the mpeg-otspec
mailing list