- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 18 Jul 2025 10:51:44 +0800
- To: www-international@w3.org
https://www.w3.org/2025/07/17-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
17 July 2025
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/events/meetings/3d8e05fe-09ac-4406-91ee-50e6ad47529d/20250717T150000/
[3] https://www.w3.org/2025/07/17-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, JcK, r12a
Regrets
-
Chair
Addison Phillips
Scribe
atsushi
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]Review RADAR Review
5. [8]Pending Issue Review
6. [9]Double-check our issue 1935
7. [10]Floating time article
8. [11]AOB?
Meeting minutes
Agenda Review
Action Items
<addison> [12]https://github.com/w3c/i18n-actions/issues
[12] https://github.com/w3c/i18n-actions/issues
<addison> #176
<gb> [13]Action 176 add WG comment to html 11395 (on aphillips)
due 2025-07-03
[13] https://github.com/w3c/i18n-actions/issues/176
<addison> #175
<gb> [14]Action 175 respond to our #2005 (on aphillips) due
2025-06-26
[14] https://github.com/w3c/i18n-actions/issues/175
addison: #176 working on
<addison> close #175
<gb> Closed [15]issue #175
[15] https://github.com/w3c/i18n-actions/issues/175
addison: #175 done
<addison> #173
<gb> [16]Action 173 ping zainab (on aphillips) due 2025-06-19
[16] https://github.com/w3c/i18n-actions/issues/173
addison: #173 haven't heard anything yet
… close this, and will take another action to ping
<addison> #169
<gb> [17]Action 169 reply to html 10843 and css 9832 (on
aphillips) due 2025-05-08
[17] https://github.com/w3c/i18n-actions/issues/169
<addison> #162
<gb> [18]Action 162 poll I18N/CSS for new day/time (on
aphillips) due 2025-03-25
[18] https://github.com/w3c/i18n-actions/issues/162
addison: #162, ping but no responce yet
… I may escalate this to CSS WG, whether WG is interested in or
not
<addison> #157
<gb> [19]Action 157 write glossary proposal identifying options
and next steps for those options (on aphillips) due 2025-02-20
[19] https://github.com/w3c/i18n-actions/issues/157
addison: so, action is done, but open another
<addison> #135
<gb> [20]Action 135 follow up on XR issue 1393 about locale in
session (on aphillips) due 2024-10-17
[20] https://github.com/w3c/i18n-actions/issues/135
<addison> #127
<gb> [21]Action 127 make a list of shared topics of interest
between TG2 and W3C-I18N (on aphillips) due 2024-09-30
[21] https://github.com/w3c/i18n-actions/issues/127
<addison> #3
<gb> [22]CLOSED Action 3 Give ghurlbot access to write to the
repo (on r12a) due 18 Jul 2023
[22] https://github.com/w3c/i18n-actions/issues/3
<addison> #33
<gb> [23]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[23] https://github.com/w3c/i18n-actions/issues/33
<addison> #7
<gb> [24]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[24] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [25]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips)
due 27 Jul 2023
[25] https://github.com/w3c/i18n-actions/issues/4
Info Share
Review RADAR Review
<addison> [26]https://github.com/orgs/w3c/projects/91/views/1
[26] https://github.com/orgs/w3c/projects/91/views/1
addison: no new incoming
… any other progress?
[silent]
Pending Issue Review
<addison> [27]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[27] https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
addison: nothing new here
Double-check our issue 1935
<addison> #1935
<gb> Issue 1935 not found
<addison> [28]i18n-activity#1935
[28] https://github.com/w3c/i18n-activity/issues/1935
<gb> [29]Issue 1935 Unicode identifiers in the WAT format (by
xfq) [close?] [needs-resolution] [s:wasm-core]
[t:markup_identifiers] [cg:webassembly]
[29] https://github.com/w3c/i18n-activity/issues/1935
addison: quick q? issue above
<addison> [30]WebAssembly/spec#1843
[30] https://github.com/WebAssembly/spec/issues/1843
<gb> [31]CLOSED Issue 1843 Unicode identifiers in the WAT
format (by xfq) [i18n-needs-resolution]
[31] https://github.com/WebAssembly/spec/issues/1843
addison: is this issue, previously discussed on character
identifiers
… told them we will not raise formal objection previously, and
in result no change made
… do we want to say anything before advancing?
addison: they only permits id with ascii
<addison> [32]WebAssembly/spec#1618
[32] https://github.com/WebAssembly/spec/issues/1618
<gb> [33]CLOSED Issue 1618 relax the var to allow utf8 encoding
in the wat syntax (by bobzhang) [i18n-tracker]
[33] https://github.com/WebAssembly/spec/issues/1618
addison: many ascii string identifier definitions have been
developed so far
<xfq> [34]WebAssembly/spec#1843
[34] https://github.com/WebAssembly/spec/issues/1843
xfq: that's old one, and filed new as above
… for clarification
… they allow escaped Unicode identifiers or just use ascii
addison: want to ask again or?
JcK: if they are sufficient with escaped identifier, should be
fine?
xfq: they require escaping for all non-ascii identifiers
<xfq> [35]WebAssembly/annotations?tab=readme-ov-file
[35] https://github.com/WebAssembly/annotations?tab=readme-ov-file
[all seeking spec text around identifier]
<addison> [36]https://www.w3.org/TR/wasm-core-2/#names%E2%91%A0
[36] https://www.w3.org/TR/wasm-core-2/#names①
<xfq> [37]https://webassembly.github.io/annotations/core/text/
values.html#text-id
[37] https://webassembly.github.io/annotations/core/text/values.html#text-id
[38]https://webassembly.github.io/spec/core/text/
lexical.html#characters
[38] https://webassembly.github.io/spec/core/text/lexical.html#characters
While source text may contain any Unicode character in comments
or string literals, the rest of the grammar is formed
exclusively from the characters supported by the 7-bit ASCII
subset of Unicode.
<r12a> [39]https://webassembly.github.io/spec/core/
bikeshed/#characters%E2%91%A0
[39] https://webassembly.github.io/spec/core/bikeshed/#characters①
<addison> [40]https://webassembly.github.io/spec/core/
bikeshed/#text-idchar
[40] https://webassembly.github.io/spec/core/bikeshed/#text-idchar
<r12a> [41]https://webassembly.github.io/spec/core/
bikeshed/#strings%E2%91%A0
[41] https://webassembly.github.io/spec/core/bikeshed/#strings①
<r12a> [42]https://webassembly.github.io/spec/core/
bikeshed/#identifiers%E2%91%A0
[42] https://webassembly.github.io/spec/core/bikeshed/#identifiers①
addison: should say anything? any good reason to ask changes?
<xfq> "Indices can be given in both numeric and symbolic form.
Symbolic identifiers that stand in lieu of indices start with
<xfq> , followed by eiter a sequence of printable ASCII
characters that does not contain a space, quotation mark,
comma, semicolon, or bracket, or by a quoted name."
<xfq> "or by a quoted name"
xfq: found that identifier itself is defined by above text
<xfq> "Names are strings denoting a literal character sequence.
A name string must form a valid UTF-8 encoding as defined by
Unicode (Section 2.5) and is interpreted as a string of Unicode
scalar values."
xfq: this is what they define
addison: close tracker issue.
<addison> close [43]i18n-activity#1935
[43] https://github.com/w3c/i18n-activity/issues/1935
<gb> Cannot close issue #1935 -> ghurlbot does not have the
correct permissions to execute `CloseIssue`
Floating time article
<xfq> [44]https://w3c.github.io/i18n-drafts/questions/
qa-floating-times.en
[44] https://w3c.github.io/i18n-drafts/questions/qa-floating-times.en
<xfq> [45]https://github.com/w3c/i18n-drafts/
issues?q=is%3Aissue%20state%3Aopen%20%5Bquestions%2Fqa-floating
-times%5D
[45] https://github.com/w3c/i18n-drafts/issues?q=is:issue state:open [questions/qa-floating-times]
xfq: we have sent out floating time article for review
… we have several issues there
addison: one reason not published is Temporal has been making
progress in JS
… best practices are still evolving on this front
… separate activity on format side
… probably not suitable to evolve until things setlled
xfq: so, wait until Temporal, and Semantic Skeletons in
Unicode?
addison: correct
… message format is under development
[situation around external development]
<xfq> [46]w3c/i18n-drafts#662
[46] https://github.com/w3c/i18n-drafts/issues/662
<gb> [47]Issue 662 Untranslated word in the Japanese
boilerplate (by xfq)
[47] https://github.com/w3c/i18n-drafts/issues/662
xfq: need to be checked by Atsushi
AOB?
<xfq> [48]w3c/i18n-drafts#622
[48] https://github.com/w3c/i18n-drafts/pull/622
<gb> [49]Pull Request 622 Initial work on address formats (by
xfq)
[49] https://github.com/w3c/i18n-drafts/pull/622
xfq: PR about address format above, should be interested by all
<addison> [50]https://github.com/w3c/i18n-drafts/blob/xfq/
address-2024/questions/qa-address-formats.en.md
[50] https://github.com/w3c/i18n-drafts/blob/xfq/address-2024/questions/qa-address-formats.en.md
addison: check preview
… still working on, or agenda+?
xfq: this is draft, Richard already give comment and under
iteration, and is fine to be agenda+
Received on Friday, 18 July 2025 02:52:00 UTC