<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 12:38 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_4476846104314844371WordSection1">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">On Friday, August 14, 2020 1:12 AM Dave Crossland wrote:<br>
<br>
</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">You'll have to forgive me for sounding rather partisan,
<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)">Forgiven! You should prioritize your sleep too!
</span><span style="font-size:11pt;font-family:Wingdings;color:rgb(31,73,125)">J</span></p></div></div></div></div></blockquote><div><br></div><div>Sadly my 8 month old manager decides when that can happen, not me ;) </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_4476846104314844371WordSection1"><div><div><p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"> </span>but emailing around docx files seems to me rather inefficient :) </p><p class="MsoNormal" style="margin-left:0.5in"><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)">Yes, it is, but there are realities we can’t change.</span></p></div></div></div></div></blockquote><div><br></div><div>Hmm :) If ISO requires a DOCX file as input, that is still compatible with the more efficient repo-based authoring process I am proposing, as it is possible to have such files generated in a programmatic way. </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_4476846104314844371WordSection1"><div><div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;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)">On top of that, the ISO SC29 have been undergoing some major org changes lately, so things are a little bit out of hands because of all the transitions happening
now. It was relatively easy to find a public link for the output document of the previous meeting, not so much (yet) for the latest one, which I emailed a copy of.</span></p></div></div></div></div></blockquote><div><br></div><div>Got it, thanks for the context. </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_4476846104314844371WordSection1"><div><div><p class="MsoNormal" style="margin-left:0.5in"><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in"><span style="font-family:Arial,sans-serif">Where are the documents referenced in (1)?<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> <u></u></span></p>
<p class="MsoNormal"><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></p></div></div></div></div></blockquote><div><br></div><div>I see. That is disappointing. Is a summary available? </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_4476846104314844371WordSection1"><div><div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> but the liaison from CSS WG is public (</span><a href="https://lists.w3.org/Archives/Public/www-archive/2020Feb/att-0005/CSS-SC29-20200113.pdf" target="_blank">https://lists.w3.org/Archives/Public/www-archive/2020Feb/att-0005/CSS-SC29-20200113.pdf</a><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">),
and I made it available as part of the original announcement back in February this year (</span><a href="https://lists.aau.at/pipermail/mpeg-otspec/2020-February/001770.html" target="_blank">https://lists.aau.at/pipermail/mpeg-otspec/2020-February/001770.html</a><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">)</span></p></div></div></div></div></blockquote><div><br></div><div>Excellent! </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_4476846104314844371WordSection1"><div><div>
</div>
<div>
<p class="MsoNormal">My suggestion about a github repo seems to fall within (3), too? :)<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;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)">The discussions we are conducting on this list as part of the AHG activities definitely fall within mandate 3.<u></u><u></u></span></p>
<p class="MsoNormal"><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://standards.iso.org/ittf/PubliclyAvailableStandards/" 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></p></div></div></div></div></blockquote><div><br></div><div>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://github.com/MPEGGroup/FileFormat">https://github.com/MPEGGroup/FileFormat</a> (and indeed, a twin with <a href="https://github.com/MicrosoftDocs/typography-issues">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. </div><div><br></div><div>Cheers</div><div>Dave </div></div></div>