<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello -</p>
<p>Adobe has a small pile of specification-related questions and
ideas that have been waiting for some sort of working/ad hoc group
to help work through them. There is no particular hurry with some
of them, especially given the more pressing topics recently
discussed here, so we are holding off with those. (They're mostly
CFF related.)<br>
</p>
<p>However, there are three issues that may be of general interest
and might be good to fix on a shorter schedule. Each relates to
details of the variable font part of the OTF specification. <br>
</p>
<p>Dave Crossland has suggested that we start using the
OpenFontFormat GitHub repository for technical discussions, so I
have created an issue there for each topic:</p>
<ul>
<li><a
href="https://github.com/MPEGGroup/OpenFontFormat/issues/52">Issue
52: Need for means of distinguishing "interface
default/representative instance" from format default </a><br>
</li>
<li><a
href="https://github.com/MPEGGroup/OpenFontFormat/issues/53">Issue
53: Variable substitution: Too many regions with mixed
features </a><br>
</li>
<li><a
href="https://github.com/MPEGGroup/OpenFontFormat/issues/54">Issue
54: Variable substitution: No mechanism for interdependent
axes</a> <br>
</li>
</ul>
<p>I'm also attaching some PDF documentation on these questions. The
document on the two variable substitution issues has a bit more
background. <br>
</p>
<p>I would say that at this point issue 52 should be considered an
actual Adobe proposal; all that remains is to see if people agree
and then craft the specific changes to be added to the spec. The
other two issues are at an earlier stage and would benefit from
more discussion. <br>
</p>
<p>Skef Iterum<br>
</p>
</body>
</html>