Meeting minutes
Agenda Review
bert: one agenda+
addison: also added
bert: MathML core, close waiting resolution
Action Items
<addison> https://
<addison> #147
<gb> Action 147 Follow up on normativity warnings about glossary (on aphillips)
<addison> #146
addison: need to go back conversation, and see what will happen, pending
<gb> Action 146 create new calendar entry for I18N+CSS (on aphillips) due 2024-11-28
addison: new calendar invite sent
<addison> close #146
<gb> Closed issue #146
<addison> #145
<gb> Action 145 publish timezone for wide review (on aphillips) due 2024-11-28
addison: done previously
xfq: addison to send email about this
<addison> #144
<gb> Action 144 remind everyone to read the language negotiation article (on aphillips) due 2024-11-28
<addison> close #144
<gb> Closed issue #144
<addison> #143
<gb> Action 143 make comments on the encoding issue attached to i18n-activity#1940 (on aphillips) due 2024-11-28
<addison> #142
<gb> Action 142 check if we can publish the new version of jlreq (on himorin) due 2024-11-21
<addison> #141
<gb> Action 141 set up IETF reviews requested by mnot@ et al (on xfq) due 2024-11-14
xfq: sent pending requests and added labels to track comments
<addison> close #141
<gb> Closed issue #141
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
<addison> #134
addison: will work on #135
<gb> Action 134 file an issue about making input respect locale (on aphillips) due 2024-10-05
<gb> CLOSED Action 13 Make sure generics are comfortable to read in the content language (on frivoal) due 18 Jul 2023
<addison> close #134
<gb> Closed issue #134
addison: added needs-resolution, and wait for response
<addison> #127
<gb> Action 127 make a list of shared topics of interest between TG2 and W3C-I18N (on aphillips) due 2024-09-30
<addison> #125
<gb> Action 125 propose creating a UTR for text-emphasis skip if we can get help with maintain (on aphillips) due 2024-09-30
<addison> #114
<gb> Action 114 read through i18n-activity#1659 and report on whether we're satisfied (on r12a) due 2024-08-22
r12a: connected to wider stuff, suggest to close
<addison> i18n-activity#1659
<gb> Issue 1659 [css-text-4] Add 'text-spacing: trim-all'? (by w3cbot) [close?] [tracker] [s:css-text] [i:spacing] [spec-type-issue] [jlreq] [clreq] [advice-requested] [t:typ_misc] [wg:css] [script-jpan]
<addison> close #114
<gb> Closed issue #114
<addison> #90
<gb> Action 90 steal some of henri's text from scroll-to-text-fragment for string-search (on aphillips) due 2024-04-18
<addison> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #7
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips) due 27 Jul 2023
Info Share
addison: cldr to approve message format, and issue new version of cldr by end of year
<r12a> https://
r12a: new script table above
… 79 scripts supported
[chat around rtl]
JcK: message format, two IETF WG is working on similar point
RADAR Review
<addison> https://
addison: three new one
xfq: can ask about real deadline
addison: have we established protocol?
… usually, sending issue via email to them
addison: will them make similar request in future?
xfq: currently they haven't had any similar formal review items, they mentioned this via IETF meeting, Mark sent email to PLH but no reply
addison: someone need to be assigned to these IETF-W3C communication
JcK: IETF-ICANN-WHATWG loop for IDNA, and pushing to new version of IDNA
xfq: will take IDNA
addison: take Modern Network Unicode, some comments, but not wrote down
… can take Unicode character repertoire subsets
xfq: found no issue for DAPT
Pending Issue Review
<addison> https://
String-Search PR
addison: any comment before merging?
Language/Locale Negotiation Article
[no objection to merge]
<addison> w3c/
<gb> Pull Request 581 Initial work on language-negotiation materials (by aphillips)
addison: one point to welcome update is on table, anyone need more time to check?
bert: looks fine
<xfq> +1 to merge
addison: will bring to wide review, after merging
TAG/I18N string recommendations
<addison> https://
addison: email thread above
<addison> w3ctag/
<gb> Issue 454 I18N string best practices vs. design-principles (by aphillips) [Status: In Progress] [Status: Consensus to write] [Agenda+] [i18n-needs-resolution]
addison: filed one issue to TAG for design document
… on DOM string
<addison> https://
xfq: DOMString is recommended over USVString
addison: as INFRA does
xfq: second paragraph is on handling, didn't seems clear
r12a: DOMString is default?
… danger is to list USVString
xfq: specify algorithm or process seems too general, than first paragraph on porotcol
xfq: give some example to our documents?
addison: seeking how to tell people what I mean..
… simple matching could also work by byte string
[comparison around and discussion]
addison: will seek around and try to say something
ACTION: addison: propose specdev text related to design-principles#464 discussion
<gb> Created action #148
close some WAI ACT review issues
<Bert> w3c/
<gb> Issue 1909 Should ACT require the formats for rules to be localizable? (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
bert: WG proposed to turn localizable, and change acceptable. propose to close
… answer in issue, possibly updated
r12a: they say i18n easier, but not l10n
<addison> > In addition to supporting people with disabilities, using an accessible format also makes internationalization of ACT Rules easier.
<Bert> w3c/
<gb> Issue 1912 Is the ‘descriptive title’ used for matching? (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]
addison: our guidance is to have direction and language
<Bert> w3c/
<gb> Issue 1911 ACT does not require that the language of text is indicated (by bert-github) [needs-resolution] [wg:ag] [s:act-rules-format]