Weekly github digest (Tracker items)

Issues
------
* w3c/i18n-activity (+1/-4/💬2)
  1 issues created:
  - [css-text-4] Way to only hyphenate when word is broken in “emergency situations”? (by himorin)
    https://github.com/w3c/i18n-activity/issues/831 [i:hyphenation] [s:css-text] [spec-type-issue] [tracker] 

  2 issues received 2 new comments:
  - #775 Add informative note to tts:fontStyle recommending use of tts:shear instead of tts:fontStyle="italic" for Japanese text. (1 by xfq)
    https://github.com/w3c/i18n-activity/issues/775 [s:ttml-imsc] [tracker] 
  - #589 truncation to 64-byte upper limit doesn't mention character boundaries (1 by aphillips)
    https://github.com/w3c/i18n-activity/issues/589 [close?] [needs-resolution] [s:webauthn] 

  4 issues closed:
  - Display name content rules? https://github.com/w3c/i18n-activity/issues/208 [close?] [i18nwg-agreed-to-close] [needs-resolution] [s:webauthn] 
  - Examples should include non-ASCII [editorial] https://github.com/w3c/i18n-activity/issues/207 [close?] [i18nwg-agreed-to-close] [needs-resolution] [s:webauthn] 
  - Fix #593 - Refer to RFC 8266 for RP-controlled UI strings #878 https://github.com/w3c/i18n-activity/issues/567 [close?] [i18nwg-agreed-to-close] [s:webauthn] [tracker] 
  - truncation to 64-byte upper limit doesn't mention character boundaries https://github.com/w3c/i18n-activity/issues/589 [close?] [i18nwg-agreed-to-close] [needs-resolution] [s:webauthn] 



Pull requests
-------------
* w3c/i18n-activity (+1/-0/💬0)
  1 pull requests submitted:
  - updated link from http: to https: for w3.org, w3c.github.io (by himorin)
    https://github.com/w3c/i18n-activity/pull/830 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/i18n-activity