<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">MPEG-OTSPEC subscribers and FTCG participants,</div><div class=""><br class=""></div>This is to announce that the Font and Text Community Group (FTCG)’s <b class="">GitHub repo</b> is now available, and you should <b class="">review the proposed charter by 5 October</b>. See the following post for details:<div class=""><br class=""></div><div class=""><a href="https://www.w3.org/community/font-text/2020/09/26/github-repo-and-proposed-charter/" class="">https://www.w3.org/community/font-text/2020/09/26/github-repo-and-proposed-charter/</a></div><div class=""><br class=""></div><div class="">From now on, all discussions meant for the FTCG should happen in the GitHub repo as “issues”. You don’t have to be a formal <a href="https://www.w3.org/community/font-text/participants" class="">FTCG participant</a> to join the discussions.</div><div class=""><br class=""></div><div class="">You are welcome to open any topics and questions in the FTCG GitHub’s repo about font and text’s encoding, format, shaping, layout, etc. We are also be happy to triage your questions and redirect them to relevant parties, so don’t worry about a predefined “scope”. We need to encourage communication across and around this little industry.</div><div class=""><br class=""></div><div class="">I’d like to thank Vlad for having offered this mailing list as a temporary venue, when we were still figuring out how to set up the new group (which has become the FTCG).</div><div class=""><div class="">
<br class="">Best,<br class="">梁海 Liang Hai, acting chair of the FTCG<br class=""><a href="https://lianghai.github.io" class="">https://lianghai.github.io</a>
</div>
<br class=""></div></body></html>