<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 14, 2020 at 1:32 PM Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com">Vladimir.Levantovsky@monotype.com</a>> wrote:<br></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_-5942043016270797481WordSection1">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">On Friday, August 14, 2020 1:10 PM Dave Crossland wrote:<br>
<br>
</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:11.55pt">On Fri, Aug 14, 2020 at 12:38 PM Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com" target="_blank">Vladimir.Levantovsky@monotype.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:11.55pt">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Input documents (as is the case here) are produced by their contributing members and it’s up to them whether they decide to make them public. In this particular case, the liaison
letter from SC34 isn’t public and is only accessible to accredited members of the SC29 behind the login,</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal" style="margin-left:11.55pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:11.55pt">I see. That is disappointing. Is a summary available? <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> </span><span style="color:rgb(31,73,125)">Murata-san has been directly involved in the process of authoring the SC34 liaison, I’d like to delegate it to him to provide us with the summary.</span></p></div></div></div></div></div></blockquote><div><br></div><div>Great! </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_-5942043016270797481WordSection1"><div><div><div><p class="MsoNormal"><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:24.45pt">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">The discussions we are conducting on this list as part of the AHG activities definitely fall within mandate 3.</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:24.45pt">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">However, when it comes to creating a GitHub repo - it may not be as easy as we might hope. Ideally, having the whole text of OFF in public GitHub repo would be a good thing, and each
proposed change would have an associated set of issues attached, but I am not sure how to get around copyrights issue – I am trying to get guidance on this. Even though ISO/IEC 14406-22 “Open Font Format” is a publicly available document (</span><a href="https://protect-us.mimecast.com/s/LSjsC82xAMh63JPAf2lHnb/" target="_blank">https://standards.iso.org/ittf/PubliclyAvailableStandards/</a><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">)
and anyone can get their own free copy of it – you do have to click through the copyright disclaimer before ISO allows you to download a copy. In essence, every user gets a copy that is directly licensed to him/her, it’s free to use but not free for all.</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal" style="margin-left:24.45pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:24.45pt">Understood. Well, it seems per David Singer's later (amazing! Thank you David!) comments on this list that a issue-only repo like <a href="https://protect-us.mimecast.com/s/NTHFC9ryBDhknZN6uO5_U-" target="_blank">https://github.com/MPEGGroup/FileFormat</a> (and
indeed, a twin with <a href="https://protect-us.mimecast.com/s/-B7lC0Rmp0uGvEg9uOQrnF" target="_blank">https://github.com/MicrosoftDocs/typography-issues</a> that avoids the issues with single-vendor no-policy spaces) would still be useful, as it could move more concrete
discussions off this list to a place where they can be better tagged, sorted, segmented into milestones, tied to resolution actions, and so on - and this list could return to a lower level of traffic for discussions that are more meta or free wheeling. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Yes, absolutely, but I am still hopeful that maybe (fingers crossed) we can do more.</span></p></div></div></div></div></div></blockquote><div><br></div><div>Perhaps such a repo will be a good place for Murata-san to publish such a summary. </div><div><br></div><div>Would you be able to reach out to an admin of the <a href="http://github.com/MPEGGroup">github.com/MPEGGroup</a> github org and ask them to create a <a href="http://github.com/MPEGGroup/OpenFontFormat">github.com/MPEGGroup/OpenFontFormat</a> repo? :) </div><div><br></div><div>Cheers<br>Dave </div></div></div>