– DRAFT –
Internationalization Working Group Teleconference

Agenda Review

Action Items

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

<addison> #182

<gb> Action 182 respond to CSS, cancel existing call, propose ideas for future cooperation per today's telecon (on aphillips) due 2025-08-14

addison: responded to them, and cancel one for this month, will continue discussion

<addison> close #182

<gb> Closed issue #182

<addison> #181

<gb> Action 181 schedule topic to review server config articles/materials per 2025-08-07 call (on aphillips) due 2025-08-14

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

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

addison: close this one, #157

<addison> close #157

<gb> Closed issue #157

addison: xfq, you made PR on this point, and in agenda point in sometime future (or this week)

<addison> #151

<gb> Action 151 look into the line height of text containing emphasis marks, CSSWG issue # 11257 (on fantasai) due 2024-12-24

<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: done on this

<addison> #125

<gb> Action 125 propose creating a UTR for text-emphasis skip if we can get help with maintain (on aphillips) due 2024-09-30

addison: 125, CSS action item

<addison> close #125

<gb> Closed issue #125

<addison> #33

<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)

addison: will clean up and check potential next steps

<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

JcK: [small voice

addison: long standing WHATWG tracking issues on these
… WG is actioned to work on fixing email address one
… surprised IETF was not aware

JcK: WG is concerned on that
… particulally on @@@1

<r12a> Universal Acceptance Expert Working Group

r12a: joined @@@2
… no idea on @@@3

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

addison: need some clean up here

<r12a> https://www.w3.org/staff/

r12a: there is update on official titles

Follow up on TG2 and CSS Conversations

addison: later today TG2 call

xfq: in their repo, they also can label issue as i18n

Gap could be misunderstood as a literal typographic gap

<xfq> w3c/clreq#694

<gb> Issue 694 Gap could be misunderstood as a literal typographic gap (by YDX-2147483647)

xfq: basically issue 694, we have many gap analysis documents
… could be misunderstood as a literal typographic gap

addison: any disagreement?

Add a JavaScript Internationalization article

<xfq> https://github.com/w3c/i18n-drafts/blob/xfq/intl/articles/intl/index.en.md

xfq: above on JS intl point, r12a gave some comments
… JS has intl object for i18n

<addison> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl

xfq: listing features could be useful for others
… MDN doc is also useful for developers, I've found

addison: posted URL of MDN start page for Intl object
… best to summarise, or any good way
… some document like how to use Intl object effective way for Web content
… could be easy to list existing document as references

xfq: in MDN lots of information are listed as reference

addison: every single options are properly documented

xfq: on our point of view, we have lots of articles on Web applications creators, and internationalized web sites
… this is on creating web sites, and Intl are oriented as guide

r12a: suggesting to @@@4 MDN documents

<xfq> https://github.com/w3c/i18n-drafts/commit/e025bc41686cf2da46a6d8bb7db31f188bc94bf4#r163967615

xfq: will continue working, and get comments possibly next week or some

glossary structure with normative and non-normative

<xfq> https://deploy-preview-84--i18n-glossary.netlify.app/

<xfq> w3c/i18n-glossary#84

<gb> Pull Request 84 Divide the glossary by normativity (by xfq)

xfq: preview of PR on alpha version of separating glossary into normative and non-normative
… based on what we want to transform document into
… split terms into two sections
… terms with entry in INFRA or some other places as normative
… did not change any of definitions
… removed alphabetic index
… created two search boxes for convinience to put keywords for two sections

xfq: would include both terms and definitions, or I could include option to hide definitions

addison: without exact term in mind, you can find via keyword in definitions

addison: we should have higher level of conversation first
… which term should fall into which
… having two words list, harder to seek
… currently division is not solid, like some normative definitions refers non-normative

xfq: granurality of normative section have some restriction on respec

<Bert> (I think I'd prefer a single list, and the normative terms flagged some way, maybe by giving them a border...)

addison: some non-normative definitions in whole normative document, with some note on divisions
… we have to explain terms and definitions in non-normative as useful definitions
… we actually want to use these terms in other our documents

<xfq> https://www.w3.org/TR/clreq/#glossary

<xfq> it adds a <mark style="background-color: yellow; font-weight: bold;"> to the keyword

addison: we should think with collecting ideas for getting forward

AOB?

[none]