– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

<addison> https://github.com/w3c/i18n-actions/issues

<addison> #176

<gb> Action 176 add WG comment to html 11395 (on aphillips) due 2025-07-03

<addison> #175

<gb> Action 175 respond to our #2005 (on aphillips) due 2025-06-26

addison: #176 working on

<addison> close #175

<gb> Closed issue #175

addison: #175 done

<addison> #173

<gb> Action 173 ping zainab (on aphillips) due 2025-06-19

addison: #173 haven't heard anything yet
… close this, and will take another action to ping

<addison> #169

<gb> Action 169 reply to html 10843 and css 9832 (on aphillips) due 2025-05-08

<addison> #162

<gb> Action 162 poll I18N/CSS for new day/time (on aphillips) due 2025-03-25

addison: #162, ping but no responce yet
… I may escalate this to CSS WG, whether WG is interested in or not

<addison> #157

<gb> Action 157 write glossary proposal identifying options and next steps for those options (on aphillips) due 2025-02-20

addison: so, action is done, but open another

<addison> #135

<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17

<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> #3

<gb> CLOSED Action 3 Give ghurlbot access to write to the repo (on r12a) due 18 Jul 2023

<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

Review RADAR Review

<addison> https://github.com/orgs/w3c/projects/91/views/1

addison: no new incoming
… any other progress?

[silent]

Pending Issue Review

<addison> https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending

addison: nothing new here

Double-check our issue 1935

<addison> #1935

<gb> Issue 1935 not found

<addison> i18n-activity#1935

<gb> Issue 1935 Unicode identifiers in the WAT format (by xfq) [close?] [needs-resolution] [s:wasm-core] [t:markup_identifiers] [cg:webassembly]

addison: quick q? issue above

<addison> WebAssembly/spec#1843

<gb> CLOSED Issue 1843 Unicode identifiers in the WAT format (by xfq) [i18n-needs-resolution]

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> WebAssembly/spec#1618

<gb> CLOSED Issue 1618 relax the var to allow utf8 encoding in the wat syntax (by bobzhang) [i18n-tracker]

addison: many ascii string identifier definitions have been developed so far

<xfq> WebAssembly/spec#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> WebAssembly/annotations?tab=readme-ov-file

[all seeking spec text around identifier]

<addison> https://www.w3.org/TR/wasm-core-2/#names%E2%91%A0

<xfq> https://webassembly.github.io/annotations/core/text/values.html#text-id

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> https://webassembly.github.io/spec/core/bikeshed/#characters%E2%91%A0

<addison> https://webassembly.github.io/spec/core/bikeshed/#text-idchar

<r12a> https://webassembly.github.io/spec/core/bikeshed/#strings%E2%91%A0

<r12a> https://webassembly.github.io/spec/core/bikeshed/#identifiers%E2%91%A0

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 i18n-activity#1935

<gb> Cannot close issue #1935 -> ghurlbot does not have the correct permissions to execute `CloseIssue`

Floating time article

<xfq> https://w3c.github.io/i18n-drafts/questions/qa-floating-times.en

<xfq> https://github.com/w3c/i18n-drafts/issues?q=is%3Aissue%20state%3Aopen%20%5Bquestions%2Fqa-floating-times%5D

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> w3c/i18n-drafts#662

<gb> Issue 662 Untranslated word in the Japanese boilerplate (by xfq)

xfq: need to be checked by Atsushi

AOB?

<xfq> w3c/i18n-drafts#622

<gb> Pull Request 622 Initial work on address formats (by xfq)

xfq: PR about address format above, should be interested by all

<addison> 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+