W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2018

Daily github digest (WG INTERNAL review issues)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Fri, 12 Oct 2018 00:01:25 +0000
To: public-i18n-core@w3.org
Message-Id: <E1gAktR-0002q4-91@uranus.w3.org>



Issues
------
* w3c/i18n-activity (+0/-10/💬0)
  10 issues closed:
  - Incorporate CSS advances into TTML vertical text handling https://github.com/w3c/i18n-activity/issues/356 [close?] [recycle] [spec-type-issue] [ttml] [vertical-text] 
  - Sideways shouldn't be tied to tblr vs tbrl https://github.com/w3c/i18n-activity/issues/358 [close?] [ttml] 
  - Default directions in mixed textOrientation should use TR50 https://github.com/w3c/i18n-activity/issues/357 [close?] [spec-type-issue] [ttml] [vertical-text] 
  - Upright orientation involves more than just glyph orientation https://github.com/w3c/i18n-activity/issues/359 [close?] [recycle] [spec-type-issue] [ttml] [vertical-text] 
  - Styling using tts:direction: should there be an auto value? https://github.com/w3c/i18n-activity/issues/328 [close?] [recycle] [ttml] 
  - No mention of isolation for directional controls https://github.com/w3c/i18n-activity/issues/346 [close?] [ttml] 
  - Link from tts:direction to tts:writing-mode https://github.com/w3c/i18n-activity/issues/343 [close?] [ttml] 
  - Use a more typical example for tts:direction https://github.com/w3c/i18n-activity/issues/344 [close?] [ttml] 
  - Why not use elements for ruby? https://github.com/w3c/i18n-activity/issues/313 [close?] [ttml] 
  - Meaning of 'glyph area descendant' https://github.com/w3c/i18n-activity/issues/311 [close?] [recycle] [ttml] 




Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/i18n-activity
Received on Friday, 12 October 2018 00:01:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:02:26 UTC