<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>This is the current status of Adobe's proposals, in advance of
next week's Ad Hoc meeting:</p>
<ul>
<li>"negation" is unchanged:
<a class="moz-txt-link-freetext" href="https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/negation.pdf">https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/negation.pdf</a></li>
<li>"cff2hintorder": Peter and I discussed this over email and
concluded that this counts as a couple of clarifications of what
had been ambiguous rather than outright changes. We tentatively
decided that he would edit the language and roll the content in
through his ongoing OpenType synchronization project. We can
discuss this approach at the meeting if anyone has concerns. The
(unedited original) document is still
<a class="moz-txt-link-freetext" href="https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/cff2hintorder.pdf">https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/cff2hintorder.pdf</a></li>
<li>I gave "varchintguide" a substantial editing pass.
<a class="moz-txt-link-freetext" href="https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/varchintguide.pdf">https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/varchintguide.pdf</a></li>
<li>I gave "newfeatvar_spec" an editing pass as well. Note that
the Microsoft reps have not yet had an opportunity to take up
their concerns from the last meeting about this with me, but I'm
hoping that can still happen before next Tuesday.
<a class="moz-txt-link-freetext" href="https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/newfeatvar_spec.pdf">https://github.com/adobe-type-tools/opentype-spec-drafts/blob/main/newfeatvar_spec.pdf</a></li>
</ul>
<p>Thanks,<br>
Skef<br>
</p>
</body>
</html>