- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 14 Jun 2024 14:06:03 +0800
- To: www-international@w3.org
https://www.w3.org/2024/06/13-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
13 June 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240613T150000/
[3] https://www.w3.org/2024/06/13-i18n-irc
Attendees
Present
Addison, Fuqiao, JcK, Richard
Regrets
Bert
Chair
Addison Phillips
Scribe
xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]I18N WG/IG recharter
7. [10]String-Meta Consumer guidance PR
8. [11]I18N+CSS prep
9. [12]AOB?
10. [13]Summary of action items
Meeting minutes
Agenda Review
Action Items
addison: is there anything else we need to add to the agenda?
<addison> [14]https://github.com/w3c/i18n-actions/issues
[14] https://github.com/w3c/i18n-actions/issues
<addison> #105
<gb> [15]Action 105 Review
https://deploy-preview-87--string-meta.netlify.app/#bp-consumer
s (on r12a) due 2024-06-13
[15] https://github.com/w3c/i18n-actions/issues/105
<addison> #104
<gb> [16]Action 104 follow up on action#4 by writing an email
(on aphillips) due 2024-06-13
[16] https://github.com/w3c/i18n-actions/issues/104
<addison> #4
<gb> [17]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips,
r12a) due 27 Jul 2023
[17] https://github.com/w3c/i18n-actions/issues/4
<addison> #103
<gb> [18]Action 103 Migrate RADAR project (on aphillips)
[18] https://github.com/w3c/i18n-actions/issues/103
addison: #103, it's a little more complicated since I clicked
on the first step
<addison> #102
<gb> [19]Action 102 ping alreq group to review our
i18n-activity#1620 (on aphillips) due 2024-05-30
[19] https://github.com/w3c/i18n-actions/issues/102
addison: if I run into anything, I may ping you
<addison> [20]i18n-activity#1620
[20] https://github.com/w3c/i18n-activity/issues/1620
<gb> [21]Issue 1620 [focusgroup] i18n: should arrow key
navigation follow text direction? (by w3cbot) [close?]
[tracker] [needs-attention] [s:open-ui] [cg:open-ui]
[21] https://github.com/w3c/i18n-activity/issues/1620
addison: #102, I did send emails to those lists and I don't
think anybody's responded
… anybody gonna look or should I nudge again?
xfq: we can raise github issues
r12a: they're not terribly active at the moment
… Najib often comments on things but the hlreq folks haven't
been active for a while now
<addison> #101
<gb> [22]Action 101 research what if anything to do with
dpub-pagination comments and old DPIG comments (on xfq) due
2024-05-30
[22] https://github.com/w3c/i18n-actions/issues/101
<addison> #99
<gb> [23]Action 99 ping unicode about emphasis skip property
(see our #530) (on aphillips) due 2024-05-28
[23] https://github.com/w3c/i18n-actions/issues/99
xfq: #101, still pending
addison: #99, done
… will bring it up with CSS in the upcoming call with them
<addison> #9
<gb> [24]CLOSED Action 9 Follow up with ecma-402 on next steps
and start tc39 discussion (on aphillips) due 18 Jul 2023
[24] https://github.com/w3c/i18n-actions/issues/9
#98
<gb> [25]Action 98 fix code points examples in
lang-bidi-use-cases (on r12a) due 2024-05-23
[25] https://github.com/w3c/i18n-actions/issues/98
<addison> #96
<gb> [26]Action 96 evaluate and where necessary fix
i18n-glossary#76 (on r12a) due 2024-05-02
[26] https://github.com/w3c/i18n-actions/issues/96
<addison> #93
<gb> [27]Action 93 create best practices for consumers in
string-meta (on aphillips) due 2024-04-25
[27] https://github.com/w3c/i18n-actions/issues/93
<addison> #90
<gb> [28]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[28] https://github.com/w3c/i18n-actions/issues/90
<addison> #89
<gb> [29]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[29] https://github.com/w3c/i18n-actions/issues/89
<addison> #87
<gb> [30]Action 87 write to IETF ADs about RFC9457 with JcK's
assistance (on aphillips) due 2024-04-04
[30] https://github.com/w3c/i18n-actions/issues/87
addison: #87, done
close #87
<gb> Closed [31]issue #87
[31] https://github.com/w3c/i18n-actions/issues/87
ACTION: addison: write to ietf group about rfc9457
<gb> Created [32]action #106
[32] https://github.com/w3c/i18n-actions/issues/106
<addison> close #87
<gb> Closed [33]issue #87
[33] https://github.com/w3c/i18n-actions/issues/87
<addison> #79
<gb> [34]Action 79 schedule a follow-up call with WHATNOT in
~April (on aphillips) due 2024-03-07
[34] https://github.com/w3c/i18n-actions/issues/79
<addison> #78
<gb> [35]Action 78 compare infra to i18n-glossary export list
and report back (on aphillips) due 2024-03-07
[35] https://github.com/w3c/i18n-actions/issues/78
<addison> #33
<gb> [36]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[36] https://github.com/w3c/i18n-actions/issues/33
<addison> #8
<gb> [37]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[37] https://github.com/w3c/i18n-actions/issues/8
<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,
r12a) due 27 Jul 2023
[39] https://github.com/w3c/i18n-actions/issues/4
Info Share
<r12a> [40]https://www.unicode.org/events/
[40] https://www.unicode.org/events/
<r12a> [41]https://us06web.zoom.us/webinar/register/
7317157843728/WN_wtqmIMS-ScasVMSqMCUYOw#/registration
[41]
https://us06web.zoom.us/webinar/register/7317157843728/WN_wtqmIMS-ScasVMSqMCUYOw#/registration
r12a: Bidirectional Text (Part 1): The Basics of Bidi
… register here ^
RADAR Review
r12a: we have 3 documents for publication
… Kashmiri, Uighur, and Urdu
<addison> [42]https://github.com/w3c/i18n-request/projects/1
[42] https://github.com/w3c/i18n-request/projects/1
r12a: will be published on Tuesday
xfq: haven't done HTML Ruby Markup Extensions
addison: Device Posture API is mine
… I have one minor comment
… we will review it in a minute
Pending Issue Review
atsushi: I have an issue on Controllers Documents
<addison> [43]i18n-activity#1860
[43] https://github.com/w3c/i18n-activity/issues/1860
<gb> [44]Issue 1860 type should be defined as identical to but
not contain (by himorin) [pending] [wg:vc]
[s:controller-document]
[44] https://github.com/w3c/i18n-activity/issues/1860
atsushi: I believe they want to match strings values in a JSON
format
… but they do not refer to the string comparison def in Infra
[45]https://infra.spec.whatwg.org/#string-is
[45] https://infra.spec.whatwg.org/#string-is
atsushi: I suppose they mean 'identical to'
addison: that doesn't seem like an i18n comment
… I'll tag that as non-i18n and then you can pass that along
atsushi: OK
<addison> [46]i18n-activity#1859
[46] https://github.com/w3c/i18n-activity/issues/1859
<gb> [47]Issue 1859 Device posture and direction interaction
(by aphillips) [pending] [needs-resolution] [t:bidi_inline]
[s:device-posture]
[47] https://github.com/w3c/i18n-activity/issues/1859
addison: I'll move controller-document to Completed
… since we're not going to track that issue
addison: my issue is #1859
<gb> Issue 1859 not found
addison: it's on the device posture spec
… device posture is whether a device is flat or folded
… they have an explainer about how device posture interacts
with some other things
… so you can find out how the viewports are arranged
… and one of the interesting things is whether directionality
might affect how things are arranged
… when you fold the device like a book
… anybody need more time?
I18N WG/IG recharter
addison: I'll forword
[48]https://lists.w3.org/Archives/Member/member-i18n-core/
2024Jun/0003.html
[48]
https://lists.w3.org/Archives/Member/member-i18n-core/2024Jun/0003.html
xfq: Our WG and IG charter will expire at the end of September.
I have prepared new charters for these two groups. They are
mostly an extension of the current charters.
addison: need to rejoin the group after rechartering?
xfq: don't think so
… the scope is not changed
String-Meta Consumer guidance PR
<addison> [49]https://
deploy-preview-87--string-meta.netlify.app/#bp-consumers
[49]
https://deploy-preview-87--string-meta.netlify.app/#bp-consumers
addison: does anybody have comments?
I18N+CSS prep
addison: we have a call with CSS on Tuesday
<addison> [50]https://github.com/w3c/i18n-activity/
issues?q=is%3Aopen+is%3Aissue+label%3AAgenda%2BI18N%2BCSS
[50]
https://github.com/w3c/i18n-activity/issues?q=is:open+is:issue+label:Agenda+I18N+CSS
addison: in addition to the item we mentioned earlier we only
have 3 things on our list
r12a: there's been some discussion around quote
… the q element
<addison> [51]w3c/i18n-activity#969
[51] https://github.com/w3c/i18n-activity/issues/969
<gb> [52]Issue 969 [css-content] Quote character choice must
depend on surrounding language, not language of the quotation
(by w3cbot) [s:css-content] [i:quotations] [needs-resolution]
[t:typ_misc] [wg:css]
[52] https://github.com/w3c/i18n-activity/issues/969
r12a: and how to choose quote marks
… maybe we should have some discussion on that
… in this meeting
<r12a> [53]w3c/csswg-drafts#5478
[53] https://github.com/w3c/csswg-drafts/issues/5478
<gb> [54]Issue 5478 [css-content] Quote character choice must
depend on surrounding language, not language of the quotation
(by r12a) [css-content-3] [Agenda+] [Closed Accepted by CSSWG
Resolution] [i18n-needs-resolution] [Needs Edits] [Needs
Testcase
[54] https://github.com/w3c/csswg-drafts/issues/5478
<gb> … (WPT)] [Needs Naming (Request to Bikeshed)] [Agenda+
i18n]
r12a: the CSSWG has been discussing it as well
… so perhaps we should put that on the agenda to keep the ball
rolling
addison: OK
AOB?
addison: I have added that
r12a: we could informatively introduce them to the changes
we've been making to the lreq documents
addison: OK
… I'll add that to the agenda as well
Summary of action items
1. [55]addison: write to ietf group about rfc9457
Received on Friday, 14 June 2024 06:06:05 UTC