<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="">See the message in the FTCG internal mailing list for the <b class="">password-protected Zoom meeting URL</b>: <a href="https://lists.w3.org/Archives/Member/internal-font-text/2020Nov/0000.html" class="">https://lists.w3.org/Archives/Member/internal-font-text/2020Nov/0000.html</a></div><div class=""><br class=""><div class="">If you don’t have access to it, email me at <a href="mailto:lianghai@gmail.com" class="">lianghai@gmail.com</a> to get the Zoom URL (briefly introduce yourself in your email if we don’t already know each other).</div><div class=""><br class=""></div><div class="">Really sorry for the inconvenience but we’re still figuring the process out. May try a waiting room mechanism in the future.</div></div><div class="">
<br class="">Best,<br class="">梁海 Liang Hai<br class=""><a href="https://lianghai.github.io" class="">https://lianghai.github.io</a>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Nov 10, 2020, at 05:57, 梁海 Liang Hai <<a href="mailto:lianghai@gmail.com" class="">lianghai@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">We’ve confirmed the time:<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">20:30–22:00 UTC on Tue 17 Nov</div></blockquote><div class=""><br class=""></div><div class="">(Note this is more than a day later than our earlier Monday slots.)</div><div class=""><br class=""></div><div class="">See <a href="https://github.com/w3c/font-text-cg/issues/28" class="">https://github.com/w3c/font-text-cg/issues/28</a> for details. The Zoom meeting URL will be available in the GitHub issue.<br class=""><div class="">
<br class="">Best,<br class="">梁海 Liang Hai<br class=""><a href="https://lianghai.github.io/" class="">https://lianghai.github.io</a>
</div>
<div class=""><br class=""><blockquote type="cite" class=""><div class="">On Nov 5, 2020, at 21:00, 梁海 Liang Hai <<a href="mailto:lianghai@gmail.com" class="">lianghai@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">The W3C FTCG (Font and Text Community Group) Meeting 5 has been <i class="">tentatively</i> scheduled for 17:30–19:00 UTC on Mon 16 Nov. See time zone conversion: <a href="https://everytimezone.com/s/c19c3489" class="">https://everytimezone.com/s/c19c3489</a></div><div class=""><br class="">The time is to be confirmed again with a Doodle poll: <a href="https://doodle.com/poll/9mqdrqbpga8wudvk" class="">https://doodle.com/poll/9mqdrqbpga8wudvk</a> (Your identities in the poll will only be visible to the acting chair, Liang Hai, so your privacy is better protected this time.)</div><div class=""><br class="">See the following issue ticket for a later confirmation of time and Zoom URL of Meeting 5, and also free to submit your agenda items there: <a href="https://github.com/w3c/font-text-cg/issues/28" class="">https://github.com/w3c/font-text-cg/issues/28</a></div><div class=""><br class="">The minutes of Meeting 4 has been published at: <a href="https://github.com/w3c/font-text-cg/blob/main/minutes/meeting-20201019-4.md" class="">https://github.com/w3c/font-text-cg/blob/main/minutes/meeting-20201019-4.md</a></div><div class=""><br class="">Best,<br class="">梁海 Liang Hai, acting chair of the W3C FTCG<br class=""><a href="https://lianghai.github.io/" class="">https://lianghai.github.io</a>
</div>

<br class=""></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></body></html>