– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

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

<addison> #183

<gb> Action 183 send JavaScript Intl article to wide review (on xfq) due 2025-08-28

<addison> close #183

<gb> Closed issue #183

xfq: did for #183

<addison> #171

<gb> Action 171 revise local-font-access to exclude localhost and talk more about opt-in model (on ZainabAq) due 2025-05-22

<addison> #136

<gb> Issue 136 follow up on XML errata (by aphillips) [task]

<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> #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: nothing super interesting to report

<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: we have new member

Joel: located in Utah, previously worked at Spotify, and did internationalization program at another company
… excited to be a part of team, and strongly interested in i18n education program, such as introducly documents

addison: if any of us can help you, let us know
… for this year, Unicode event conflicts with our TPAC

Review RADAR Review

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

addison: no new incoming

Pending Issue Review

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

RDF and RFC9839

<addison> #2023

<gb> Issue 2023 not found

<addison> i18n-activity#2023

<gb> Issue 2023 Consider referencing RFC 9839 to restrict problematic Unicode characters in RDF 1.2 literals and IRIs (by w3cbot) [pending] [tracker]

addison: above is our link

<addison> w3c/rdf-star-wg#177

<gb> Issue 177 Consider referencing RFC 9839 to restrict problematic Unicode characters in RDF 1.2 literals and IRIs (by domel) [i18n-tracker]

addison: while ago, we reviewed their spec and RFC, and some pointed problematic character to RFC

addison: if you can list kinds of issue points, even not complete, via charmod or UTR or else, would help to offer guidelines
… even if we don't need some references or else, these could be important for various colleagues including user, and similar to charmod or else
… trully completed checklist is quite hard to build

Number, currency, and unit formatting

<xfq> w3c/i18n-drafts#693

<gb> Pull Request 693 Initial draft on number, currency, and unit formatting (by xfq)

<addison> https://github.com/w3c/i18n-drafts/blob/xfq/issue-410/questions/qa-number-format.en.md

xfq: drafted article for number or currency or else
… got some comments from r12a or addison

<addison> "can lead misunderstanding" -> "can lead to misunderstanding"

JcK: will check coming week(s)

Joel: will check tomorrow, esp. on locale setting, one thing is attribute to be clearly stated

addison: article is for using from JavaScript or dynamic script, but still work for static page or articles
… also I have working on message format similar to this area over recent several years

<xfq> https://github.com/w3c/i18n-drafts/pull/693#discussion_r2163965722

xfq: wrote similar article, in similar format but in different text
… w3c article is little bit longer

addison: will comve back enxt week or so

Orthography term

<addison> w3c/i18n-glossary#87

<gb> Issue 87 Orthography (by xfq) [enhancement] [Agenda+]

addison: xfq questioned one, and raised to agenda on this
… two thing, whether to add this word into glossary, another is a11y colleagues are still strugguing on presentation for text string
… great guideline for western languages, but not for other languages or scripts

addison: not conivinced with current text inserted
… not to propose to solve here, but bunch of suggestions on operation

xfq: some comments came from JL-TF for a11y parts

r12a: could be difficult to limit usage of word in glossary

addison: rephase for more suitable one?
… and you can find more area to match with these materials

r12a: will they have official k-pop place?
… they decided to be under a umplifier or else

<addison> w3c/wcag#4263

<gb> Issue 4263 Internationalisation updates (normative) (by alastc) [Normative] [i18n-tracker] [i18n]

<addison> w3c/i18n-activity#1993

<gb> Issue 1993 Internationalisation updates (normative) (by w3cbot) [tracker] [s:wcag] [t:typ_misc] [wg:ag] [Agenda+]

<addison> w3c/coga#310

<gb> Issue 310 Review language specific issues for v2.0 of Content Usable (by rainbreaw) [i18n-needs-resolution] [review for next version]

[chat around COGA, WCAG)

<r12a> public-global-inclusion@w3.org

<r12a> https://www.w3.org/2025/07/30-global-inclusion-minutes.html

xfq: see almost no activity in COGA group, but related i11yissue event was wholder before aha\pah

<xfq> https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?tab=t.0#heading=h.j7rzaqx6ki33

addison: any i18n people will commit ,right?

<r12a> https://lists.w3.org/Archives/Public/public-global-inclusion/

[chat around a11y guideline document]

<r12a> https://www.w3.org/community/global-inclusion/

ACTION: addison: reply to wcag issue with comment about doing a higher level of interaction and pre-review

<gb> Created action #184

AOB?

[end]