<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Adobe has discussed these proposals internally and come to some
short-term conclusions:</p>
<ul>
<li>The vsindex clarifications are strictly editorial and would be
valuable. A draft of a proposal (<i>as </i>a proposal rather
than the more recent comments format) is attached.</li>
<li>The change to the treatment of the VariationStore length field
is not <i>strictly</i> editorial but is valuable and has a low
change of causing issues, so it is worth discussing. A proposal
for that is also attached.</li>
<li>We appreciate the issue with the FontMatrix operator and agree
it might make sense to deprecate it. However, we will need more
time internally to discuss this and dig up the history of why it
was retained. In the mean time there is vanishingly small harm
in adding the operator (when it is required) so we don't feel
there is any hurry with this.</li>
<li>The proposal to allow multiple vsindex operators in a
CharString is a very significant change that will need further
discussion both within Adobe and probably outside of it. It will
probably require bumping the CFF2 major version number (to 3,
alas). We will need to consider whether to allow the change in
the PrivateDict as well, and what that means for fallback (what
the first proposal clarifies). All of this means that this is
not the time to be discussing that change.</li>
</ul>
<p>Perhaps we can discuss the two editorial(esque) changes at our
next meeting.</p>
<p>Thanks,<br>
</p>
<div class="moz-cite-prefix">Skef Iterum<br>
Adobe, Inc.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 10/22/24 3:17 PM, Behdad Esfahbod
via mpeg-otspec wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF63+7XVEJpY3WT5A=UtQzBvGCSkS2LvCYX7cKCX3JTVw11d+g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi everyone,</div>
<div><br>
</div>
CFF2 has a file size advantage over TrueType-flavored variable
fonts, specially if one doesn't care about hinting (Android,
Apple platforms, etc) but does care about (uncompressed) size.<br>
<br>
CFF2 also alleviates some other limitations of variable-fonts
built against the gvar table. Unfortunately, it imposes its own
limitations. These are among the issues I'm going to raise.<br>
<br>
Please see:
<div><br>
</div>
<div> <a
href="https://github.com/harfbuzz/boring-expansion-spec/issues/155"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/harfbuzz/boring-expansion-spec/issues/155</a></div>
<div><br>
</div>
<div>for details of the changes I am proposing. Ideally, Adobe
folks choose to turn these ideas into proposals and push it
through the OFF standardization / OpenType integration
process. Failing that, we might want to go ahead and do it at
Google</div>
<div><br>
</div>
<div>Thanks,<br>
<div><br clear="all">
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">behdad<br>
<a href="http://behdad.org/" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://behdad.org/</a></div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
mpeg-otspec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a>
<a class="moz-txt-link-freetext" href="https://lists.aau.at/mailman/listinfo/mpeg-otspec">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a>
</pre>
</blockquote>
</body>
</html>