Weekly github digest (Tracker items)

Issues
------
* w3c/i18n-activity (+9/-10/💬11)
  9 issues created:
  - Clarify Latin-1 encoding requirements of text chunks (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1890 [pending] [tracker] 
  - Recommend iTXT over tEXt (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1889 [pending] [tracker] 
  - iTXt should be preferred (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1888 [pending] [needs-resolution] 
  - Prefer 3339 to 1123/822 date-time (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1887 [pending] [needs-resolution] 
  - iTXt language tag description needs attention (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1886 [pending] [needs-resolution] 
  - references to characters and character values (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1885 [pending] [needs-resolution] 
  - Normative reference to informative definition (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1884 [pending] [tracker] 
  - Text chunk processing should be in terms of the Encoding Standard (by w3cbot)
    https://github.com/w3c/i18n-activity/issues/1883 [pending] [tracker] 
  - Programmatically determine language of proper names and technical terms (by xfq)
    https://github.com/w3c/i18n-activity/issues/1882 [pending] [t:lang_strings] 

  11 issues received 11 new comments:
  - #1890 Clarify Latin-1 encoding requirements of text chunks (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1890 [pending] [close?] [tracker] 
  - #1889 Recommend iTXT over tEXt (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1889 [pending] [close?] [tracker] [s:png] 
  - #1888 iTXt should be preferred (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1888 [pending] [close?] [needs-resolution] 
  - #1887 Prefer 3339 to 1123/822 date-time (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1887 [pending] [close?] [needs-resolution] [s:png] 
  - #1886 iTXt language tag description needs attention (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1886 [pending] [close?] [needs-resolution] [s:png] 
  - #1885 references to characters and character values (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1885 [pending] [close?] [needs-resolution] [s:png] 
  - #1884 Normative reference to informative definition (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1884 [pending] [close?] [tracker] [s:png] 
  - #1883 Text chunk processing should be in terms of the Encoding Standard (1 by plehegar)
    https://github.com/w3c/i18n-activity/issues/1883 [pending] [close?] [tracker] [s:png] 
  - #1882 Programmatically determine language of proper names and technical terms (1 by aphillips)
    https://github.com/w3c/i18n-activity/issues/1882 [pending] [t:lang_strings] [s:wcag2ict] 
  - #1868 Are line breaks in examples ok? (1 by aphillips)
    https://github.com/w3c/i18n-activity/issues/1868 [close?] [jlreq] [clreq] [mlreq] [needs-resolution] [s:html-ruby-extensions] [wg:htmlwg] [script-jpan] 
  - #1704 Reference to BIDI should probably be UAX9 (1 by aphillips)
    https://github.com/w3c/i18n-activity/issues/1704 [close?] [s:appmanifest] [needs-resolution] [t:bidi_strings] [wg:webapps] 

  10 issues closed:
  - Clarify Latin-1 encoding requirements of text chunks https://github.com/w3c/i18n-activity/issues/1890 [pending] [close?] [tracker] 
  - Recommend iTXT over tEXt https://github.com/w3c/i18n-activity/issues/1889 [pending] [close?] [tracker] [s:png] 
  - iTXt should be preferred https://github.com/w3c/i18n-activity/issues/1888 [pending] [close?] [needs-resolution] 
  - Prefer 3339 to 1123/822 date-time https://github.com/w3c/i18n-activity/issues/1887 [pending] [close?] [needs-resolution] [s:png] 
  - iTXt language tag description needs attention https://github.com/w3c/i18n-activity/issues/1886 [pending] [close?] [needs-resolution] [s:png] 
  - references to characters and character values https://github.com/w3c/i18n-activity/issues/1885 [pending] [close?] [needs-resolution] [s:png] 
  - Normative reference to informative definition https://github.com/w3c/i18n-activity/issues/1884 [pending] [close?] [tracker] [s:png] 
  - Text chunk processing should be in terms of the Encoding Standard https://github.com/w3c/i18n-activity/issues/1883 [pending] [close?] [tracker] [s:png] 
  - Are line breaks in examples ok? https://github.com/w3c/i18n-activity/issues/1868 [close?] [jlreq] [clreq] [mlreq] [needs-resolution] [s:html-ruby-extensions] [wg:htmlwg] [script-jpan] 
  - Reference to BIDI should probably be UAX9 https://github.com/w3c/i18n-activity/issues/1704 [close?] [s:appmanifest] [needs-resolution] [t:bidi_strings] [wg:webapps] 




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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config