<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">At this stage — and for a few years now
— I have interpreted any reference to ‘OpenType 2.0’ to actually
mean ‘a significantly different future font technology, whether a
flavour of OpenType or an entirely new format, actually v2.0 or
some other version number’. It provides the context for free
thinking about new concepts, a cleaner and leaner format, etc.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If this is confusing, and we'd like to
restrict use of the term to actual OT/OFF spec revision, then I
propose NextFont as a codeword for typographic futurism.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">J.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<blockquote type="cite"
cite="mid:CAOgqPYcAQL4W-4ciGxiSqsasHoed_G0d=U_YGwN-ZLmgD0Wb_w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">On Fri, Sep 11, 2020 at 4:12 PM Levantovsky,
Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com"
moz-do-not-send="true">Vladimir.Levantovsky@monotype.com</a>>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-2514383480287283398WordSection1">
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I
did NOT say they can’t happen here, but this is
exactly the kind of decision that cannot be taken
lightly, and it is definitely not a joke!</span></p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Thanks for clarifying - so you are saying, comments made
about 1.X vs. 2.0 _are_ helpful and welcome here, but not
"in passing"? If yes, how to formalize such discussions? :)</div>
<div><br>
</div>
<div>On Github, we can have issues assigned to Milestones so
its very clear what context they are in: </div>
<div><br>
</div>
<div>1. Current Spec Changes (Editorial - no differences for
implementations, "OT 1.8.x)</div>
<div><br>
</div>
<div>1. Iterative Spec Changes (Small to medium work required
by implementations to meet the standard, "OT 1.9.x")</div>
<div><br>
</div>
<div>3. Incompatible Spec Changes (Large impact for
implementations, "OT 2.0")<br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-2514383480287283398WordSection1">
<p class="MsoNormal"><span
style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">New
specs can be written easily, but it’s the wide
adoption [not the spec itself] that we should care
about the most because, in the end, it is what
benefits users. You seem to care a lot about
consensus decisions, and this is exactly why
consensus decisions are so important.</span></p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Harfbuzz is now adopted widely (Google, Adobe, MS...) and
anyone can fork and implement anything and submit it mainly
harfbuzz. </div>
<div> </div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
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>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
John Hudson
Tiro Typeworks Ltd <a class="moz-txt-link-abbreviated" href="http://www.tiro.com">www.tiro.com</a>
Salish Sea, BC <a class="moz-txt-link-abbreviated" href="mailto:tiro@tiro.com">tiro@tiro.com</a>
NOTE: In the interests of productivity, I am currently
dealing with email on only two days per week, usually
Monday and Thursday unless this schedule is disrupted
by travel. If you need to contact me urgently, please
use some other method of communication. Thank you.</pre>
</body>
</html>