Internationalization Working Group Teleconference - 14 August 2025

https://www.w3.org/2025/08/14-i18n-minutes.html

Here is the meeting summary:

Quick recap

The WG reviewed various action items. We addressed document submission processes and reviewed a JavaScript internationalization article, with suggestions to improve its practical usage examples and formatting. The WG also discussed challenges with organizing normative and non-normative terms in their glossary, exploring search functionality and usability improvements while considering different styling options.

Next steps

All attendees to read the JavaScript Internationalization article and provide comments by next week.
Fuqiao to convert the JavaScript Internationalization article to HTML while people are reviewing it.
Fuqiao to add links to relevant MDN documentation sections within the content of the JavaScript Internationalization article.
Fuqiao to replace the French date example in the JavaScript Internationalization article with a more appropriate language example.
Fuqiao to create an alternative PR for the Glossary that uses styling to indicate normative terms rather than separating them into different sections.
Summary

Action Items and Email Authority

The team reviewed several action items, including a cancelled call with CSS and a pending review of the Server Config article. Addison mentioned that Zainab's revision might be becoming stale, and Fuqiao's pull request showing a glossary separation between normative and non-normative terms was discussed for potential review this week. John informed the group about an ongoing fierce argument in the IETF email core group regarding email address authority and inconsistencies between W3C documents, though Addison noted they have a long-standing pull request to fix email address handling in WG documents.

TC 39 TG 2

Addison led a meeting where Richard shared his recent invitation to join a 12-member panel run by ICANN. The group discussed the status of incoming requests, noting none were currently in review, and addressed the need for cleanup of pending issues. Addison mentioned an upcoming TG2 call for Ecma to discuss document submission for review, and encouraged participation since she would be unavailable. The team also discussed the potential for Ecma to integrate with WG's review process, with XFQ suggesting a possible label change to "W3C Tracker" while acknowledging the need for system re-engineering if different labels were used.

Typography Gap Misunderstanding Discussion

The team discussed concerns about the term "gap" in typography-related documents potentially being misunderstood. Addison and xfq agreed that the context was likely clear.

Enhancing JavaScript Internationalization Article

The team discussed a JavaScript internationalization article written by xfq, which provides an overview of the Intl object and its formatters for dates, times, numbers, currencies, and other data types. Addison raised concerns about the value of summarizing existing MDN documentation and suggested focusing on practical usage examples for content authors. The team agreed to improve the article by adding direct links to relevant MDN sections within the content and replacing the French date example with one from another language, likely Spanish.

Glossary Document Review

The team discussed a draft document that separates the i18n Glossary into normative and non-normative sections, with Addison and Fuqiao agreeing to have team members read and comment on it next week before converting it to HTML for final review.

Enhanced Search for Term Highlighting

Xfq presented a document with terms divided into normative and non-normative sections, and discussed a new search functionality that highlights and filters terms based on keyword input. Ri suggested improving the search by defaulting to term searches with an option to expand to include definitions, which would be more useful for finding specific terms within longer definitions.

Glossary Term Organization Improvements

The team discussed challenges with organizing normative and non-normative terms in their glossary, particularly regarding search functionality and usability. Addison and Richard expressed concerns about the current separation of terms into different buckets, suggesting that having a single glossary with clear formatting to distinguish normative terms would be more useful. The group considered implementing a feature to highlight normative terms and discussed the possibility of creating a separate exemplary PR to explore different styling options. They also touched on the need to explain the structure of the glossary and consider whether to export all non-normative terms for use in non-normative documents.