<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cordia New";
panose-1:2 11 3 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Not trying to shut anything down…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> Font compiler and rendering stack are open source<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are open source font compiler and rendering stack implementations, and that can definitely help facilitate hacking on new ideas.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just don’t confuse that with eventual adoption of new ideas: the implementation landscape is far more complex than current OSS compiler/rendering implementations.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at> <b>
On Behalf Of </b>Roderick Sheeter<br>
<b>Sent:</b> Tuesday, September 15, 2020 8:30 AM<br>
<b>To:</b> Simon Cozens <simon@simon-cozens.org><br>
<b>Cc:</b> mpeg-otspec <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] Introducing breaking changes into the spec (was: RE: [EXTERNAL] Proposal to deprecate derived search values)<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I see the hackers path as wide open! Font compiler and rendering stack are open source, we can (and IMHO should) play with implementation as early as we like without regard for business cases and spec changes. Q<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We just have to remember if we want other people to implement we need to do our due diligence at some point and get the spec updated.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Sep 15, 2020, 12:22 AM Simon Cozens <<a href="mailto:simon@simon-cozens.org" target="_blank">simon@simon-cozens.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On 15/09/2020 04:50, David Lemon wrote:<br>
> But I'd seriously emphasize Peter's points about building the business <br>
> case. I kinda get the sense Dave thinks it will all be self evident, but <br>
> that's not how business cases work. As someone who struggled to get <br>
> required buy-in for some of the main developments we use today, I can <br>
> assure you there's no such thing as a no-brainer.<br>
<br>
As much as it pains me (as a gung-ho developer) to admit this, I think <br>
you're right. Unless there are clear and compelling reasons to move to <br>
something else, it won't happen. Building both the business case and the <br>
coalition is really important.<br>
<br>
That said, I would strongly *recommend* putting the cart before the <br>
horse! Or at least allowing the cart and the horse to be in whatever <br>
order people like. For some of the people you want to have involved, a <br>
period of frenzied, anything-goes creativity about what a new font <br>
format might look like (whether here or elsewhere) will expose where the <br>
energy is and where the current pain points are much better than forcing <br>
them to articulate a business-focused justification. So long as all <br>
concerned are aware that this is just brainstorming and not every wild <br>
idea is likely to be taken up, then I think it's important not to quench <br>
that creativity too prematurely. We can attack the issue from both ends <br>
simultaneously: gather ideas and building the business case. Indeed, <br>
each will need to inform the other.<br>
<br>
To put it another way, thinking about implementation is precisely how <br>
developers express what's important to them.<br>
<br>
S<br>
_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
<a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.aau.at%2Fmailman%2Flistinfo%2Fmpeg-otspec&data=02%7C01%7C%7C5830dade35b84bba8f6208d8598c3fb6%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637357806183500235&sdata=Fx48Bma2SSGyLiwNriMHNo25r7nXdgScQytddPT3TbY%3D&reserved=0" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>