- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 06 Dec 2024 10:02:16 +0800
- To: www-international@w3.org
https://www.w3.org/2024/12/05-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
05 December 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/b7edae68-f52c-4aab-a1a6-3c37459e0786/20241205T150000/
[3] https://www.w3.org/2024/12/05-i18n-irc
Attendees
Present
addison, atsushi, Bert, JcK, r12a, xfq
Regrets
-
Chair
Addison Phillips
Scribe
atsushi
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]String-Search PR
7. [10]Language/Locale Negotiation Article
8. [11]TAG/I18N string recommendations
9. [12]close some WAI ACT review issues
10. [13]Summary of action items
Meeting minutes
Agenda Review
bert: one agenda+
addison: also added
bert: MathML core, close waiting resolution
Action Items
<addison> [14]https://github.com/w3c/i18n-actions/issues
[14] https://github.com/w3c/i18n-actions/issues
<addison> #147
<gb> [15]Action 147 Follow up on normativity warnings about
glossary (on aphillips)
[15] https://github.com/w3c/i18n-actions/issues/147
<addison> #146
addison: need to go back conversation, and see what will
happen, pending
<gb> [16]Action 146 create new calendar entry for I18N+CSS (on
aphillips) due 2024-11-28
[16] https://github.com/w3c/i18n-actions/issues/146
addison: new calendar invite sent
<addison> close #146
<gb> Closed [17]issue #146
[17] https://github.com/w3c/i18n-actions/issues/146
<addison> #145
<gb> [18]Action 145 publish timezone for wide review (on
aphillips) due 2024-11-28
[18] https://github.com/w3c/i18n-actions/issues/145
addison: done previously
xfq: addison to send email about this
<addison> #144
<gb> [19]Action 144 remind everyone to read the language
negotiation article (on aphillips) due 2024-11-28
[19] https://github.com/w3c/i18n-actions/issues/144
<addison> close #144
<gb> Closed [20]issue #144
[20] https://github.com/w3c/i18n-actions/issues/144
<addison> #143
<gb> [21]Action 143 make comments on the encoding issue
attached to i18n-activity#1940 (on aphillips) due 2024-11-28
[21] https://github.com/w3c/i18n-actions/issues/143
<addison> #142
<gb> [22]Action 142 check if we can publish the new version of
jlreq (on himorin) due 2024-11-21
[22] https://github.com/w3c/i18n-actions/issues/142
<addison> #141
<gb> [23]Action 141 set up IETF reviews requested by mnot@ et
al (on xfq) due 2024-11-14
[23] https://github.com/w3c/i18n-actions/issues/141
xfq: sent pending requests and added labels to track comments
<addison> close #141
<gb> Closed [24]issue #141
[24] https://github.com/w3c/i18n-actions/issues/141
<addison> #135
<gb> [25]Action 135 follow up on XR issue 1393 about locale in
session (on aphillips) due 2024-10-17
[25] https://github.com/w3c/i18n-actions/issues/135
<addison> #134
addison: will work on #135
<gb> [26]Action 134 file an issue about making input respect
locale (on aphillips) due 2024-10-05
[26] https://github.com/w3c/i18n-actions/issues/134
<gb> [27]CLOSED Action 13 Make sure generics are comfortable to
read in the content language (on frivoal) due 18 Jul 2023
[27] https://github.com/w3c/i18n-actions/issues/13
<addison> close #134
<gb> Closed [28]issue #134
[28] https://github.com/w3c/i18n-actions/issues/134
addison: added needs-resolution, and wait for response
<addison> #127
<gb> [29]Action 127 make a list of shared topics of interest
between TG2 and W3C-I18N (on aphillips) due 2024-09-30
[29] https://github.com/w3c/i18n-actions/issues/127
<addison> #125
<gb> [30]Action 125 propose creating a UTR for text-emphasis
skip if we can get help with maintain (on aphillips) due
2024-09-30
[30] https://github.com/w3c/i18n-actions/issues/125
<addison> #114
<gb> [31]Action 114 read through i18n-activity#1659 and report
on whether we're satisfied (on r12a) due 2024-08-22
[31] https://github.com/w3c/i18n-actions/issues/114
r12a: connected to wider stuff, suggest to close
<addison> [32]i18n-activity#1659
[32] https://github.com/w3c/i18n-activity/issues/1659
<gb> [33]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]
[33] https://github.com/w3c/i18n-activity/issues/1659
<addison> close #114
<gb> Closed [34]issue #114
[34] https://github.com/w3c/i18n-actions/issues/114
<addison> #90
<gb> [35]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[35] https://github.com/w3c/i18n-actions/issues/90
<addison> #89
<gb> [36]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[36] https://github.com/w3c/i18n-actions/issues/89
<addison> #33
<gb> [37]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[37] https://github.com/w3c/i18n-actions/issues/33
<addison> #7
<gb> [38]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[38] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [39]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips)
due 27 Jul 2023
[39] https://github.com/w3c/i18n-actions/issues/4
Info Share
addison: cldr to approve message format, and issue new version
of cldr by end of year
<r12a> [40]https://r12a.github.io/scripts/script-features/
[40] https://r12a.github.io/scripts/script-features/
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> [41]https://github.com/orgs/w3c/projects/91/views/1
[41] https://github.com/orgs/w3c/projects/91/views/1
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> [42]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[42]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
String-Search PR
addison: any comment before merging?
Language/Locale Negotiation Article
[no objection to merge]
<addison> [43]w3c/i18n-drafts#581
[43] https://github.com/w3c/i18n-drafts/pull/581
<gb> [44]Pull Request 581 Initial work on language-negotiation
materials (by aphillips)
[44] https://github.com/w3c/i18n-drafts/pull/581
<addison> [45]https://github.com/aphillips/i18n-drafts/blob/
gh-pages/articles/language-negotiation/language-negotiation.md
[45]
https://github.com/aphillips/i18n-drafts/blob/gh-pages/articles/language-negotiation/language-negotiation.md
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> [46]https://lists.w3.org/Archives/Public/
public-i18n-core/2024OctDec/0074.html
[46]
https://lists.w3.org/Archives/Public/public-i18n-core/2024OctDec/0074.html
addison: email thread above
<addison> [47]w3ctag/design-principles#454
[47] https://github.com/w3ctag/design-principles/issues/454
<gb> [48]Issue 454 I18N string best practices vs.
design-principles (by aphillips) [Status: In Progress] [Status:
Consensus to write] [Agenda+] [i18n-needs-resolution]
[48] https://github.com/w3ctag/design-principles/issues/454
addison: filed one issue to TAG for design document
… on DOM string
<addison> [49]https://w3c.github.io/
bp-i18n-specdev/#char_string
[49] https://w3c.github.io/bp-i18n-specdev/#char_string
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
[50]design-principles#464 discussion
[50] https://github.com/w3c/design-principles/issues/464
<gb> Created [51]action #148
[51] https://github.com/w3c/i18n-actions/issues/148
close some WAI ACT review issues
<Bert> [52]w3c/i18n-activity#1909
[52] https://github.com/w3c/i18n-activity/issues/1909
<gb> [53]Issue 1909 Should ACT require the formats for rules to
be localizable? (by bert-github) [needs-resolution] [wg:ag]
[s:act-rules-format]
[53] https://github.com/w3c/i18n-activity/issues/1909
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> [54]w3c/i18n-activity#1912
[54] https://github.com/w3c/i18n-activity/issues/1912
<gb> [55]Issue 1912 Is the ‘descriptive title’ used for
matching? (by bert-github) [needs-resolution] [wg:ag]
[s:act-rules-format]
[55] https://github.com/w3c/i18n-activity/issues/1912
addison: our guidance is to have direction and language
<Bert> [56]w3c/i18n-activity#1911
[56] https://github.com/w3c/i18n-activity/issues/1911
<gb> [57]Issue 1911 ACT does not require that the language of
text is indicated (by bert-github) [needs-resolution] [wg:ag]
[s:act-rules-format]
[57] https://github.com/w3c/i18n-activity/issues/1911
Summary of action items
1. [58]addison: propose specdev text related to
design-principles#464 discussion
Received on Friday, 6 December 2024 02:02:17 UTC