trackbot, prepare teleconference
<trackbot> action-982: Addison Phillips to Propose text for a stock health warning about selection/truncation e.g. on code units for inclusion in spec-dev -- due 2020-12-17 -- OPEN
<trackbot> Closed action-982.
<trackbot> action-994: Richard Ishida to Update automated welcome e-mail template -- due 2021-02-11 -- OPEN
richard: sent an email to plh; email didn't include the IG
<trackbot> Closed action-994.
<trackbot> action-999: Richard Ishida to Link between https://www.w3.org/international/articles/strings-and-bidi/ and https://w3c.github.io/i18n-drafts/articles/lang-bidi-use-cases/index.en -- due 2021-03-04 -- OPEN
<trackbot> Closed action-999.
<trackbot> action-1000: Richard Ishida to Publish lang-bidi-use-cases for wide review -- due 2021-03-04 -- OPEN
<trackbot> Closed action-1000.
<trackbot> action-1001: Richard Ishida to Publish qa-indic-graphemes -- due 2021-03-04 -- OPEN
<trackbot> Closed action-1001.
<trackbot> action-1002: Felix Sasaki to Update coga issue 246 with proposed text -- due 2021-03-04 -- OPEN
felix: done, link above, wrote a new proposal
<trackbot> Closed action-1002.
<trackbot> action-1003: Fuqiao Xue to Check personas for writing system problems like vertical, non-spacing, et al as discussed in teleconference -- due 2021-03-04 -- OPEN
fuqiao: done, filed an issue
<trackbot> Closed action-1003.
richard: wanted to mention this article
… corrected the name of the string-meta doc
… and pointed to the TR ver
… language direction lookup section, strengthened
New article draft: Can we derive base direction from language?
Action: richard: publish qa-direction-from-langauge for wide review
<trackbot> Created ACTION-1004 - Publish qa-direction-from-langauge for wide review [on Richard Ishida - due 2021-03-11].
Changes to specdev
richard: always afraid to edit specdev due to complicated markup
… wondering what to do about doc
… should we move all of the content e.g. 2.1.1 remove into separate docs
… just make this the checklist?
… or write everything into this doc
richard: add more summary text
… keep this largely the way it is
richard: want to change the markup in a number of ways
… automatically generating the links sections rather than manually editing
richard: changed TOC to allow for three levels
Specdev truncation requirements, other pull requests
bert: use just warning, not health warning
must avoid code points, should avoid typographic boundaries