Internationalization Working Group Teleconference - 25 September 2025

https://www.w3.org/2025/09/25-i18n-minutes.html

Here is the meeting summary:

Quick recap

The team discussed various technical issues and proposals related to HTML internationalization, localization, and number formatting, including input handling for East Asian characters and language tag validation. They explored processes for reviewing proposals in TC39 repositories and agreed on using automation and labels to track issues across repositories. The group also addressed challenges in improving HTML for internationalization and localization, discussing the need for browser implementer buy-in and potential collaboration with WHATWG for further development.

Next steps

Addison to nudge PLH about setting up tooling for TC39 organization repositories to work with W3C labels
Addison to review the DAPT spec PR to ensure they're not overusing 'zxx' language tags
Joel to raise an issue with CLDR about adding full-width decimal and grouping separators to their data
Eemeli to look into existing HTML issues related to time elements and internationalization capabilities
Eemeli to consider filing breakout sessions for TPAC for discussions on HTML internationalization improvements
Summary

HTML Localization and Spec Review

The team discussed several agenda items, including a numeric character input issue raised by WG and CSS, and Eemeli's interest in advancing localization (I18N) in HTML. Addison reviewed pending action items and noted that Joel had filed a comment about the geolocation spec's error interface, which Addison suggested should be addressed through a repository issue rather than a direct comment. The team also discussed a new ECMA 402 request from Emily regarding Intel number format and plural rules, with Addison volunteering to review it, though he encouraged others to also consider it.

TC39 Proposal Review Process

The group discussed setting up a process for reviewing proposals in TC39 repositories. Eemeli emphasized the need to make the process smooth and efficient, especially for bug fixes. Addison and Richard explored the possibility of using automation and labels to track issues across repositories. They agreed to add a "w3c-" prefix to labels to clarify their origin. The group also discussed the potential benefits of using their existing issue mirroring automation for TC39 repositories.

Proposal Reviews and Localization Decisions

The team discussed several ongoing proposals and reviews, including Keeping Trailing Zeros in Number Format and plural rules, with Addison noting that issues should be raised through the provided repository link. They reviewed the status of various items, such as DAPT, geolocation, and CSS Color Adjust, with Bert indicating he would continue work on the latter. The team also addressed an issue regarding localization policy for developer-facing messages, ultimately deciding to acknowledge the previous discussion and compromise reached with the relevant team.

East Asian Number Input Challenges

The team discussed challenges with input type="number" handling East Asian width characters, particularly full-width period and comma characters that cause parsing issues. Addison suggested pushing the solution upstream to Unicode/CLDR rather than implementing a custom HTML solution, as CLDR already contains locale-specific data about separators and could be extended to include East Asian width characters. The team agreed that CLDR's existing data about decimal and grouping separators could be used to solve the parsing problem without requiring normalization, though Joel noted that the current CLDR data only includes ASCII versions of these characters.

CLDR Character Representation Issues

The team discussed issues with CLDR data. They agreed to file an issue about full-width character consistency and to seek guidance on HTML implementation, noting gaps in symbol representation. Fuqiao reported on two issues with language tags, where the team recommended against mandatory validation of language tags unless specifically required, and discussed the use of 'zxx', with Addison suggesting 'zxx' as an alternative when the content is definitely non-linguistic.

'zxx' Locale Behavior Proposal

Eemeli discussed a proposal to define the behavior of the 'zxx' locale for JavaScript formatters and other tooling, aiming to provide predictable behavior for non-linguistic content. Addison noted the historical use of root and POSIX variants for similar purposes, and both Eemeli and Addison explored the potential use of 'zxx' and alternatives like empty strings or other locale identifiers. Addison suggested reviewing the proposal to ensure it does not overuse 'zxx' and to consider the context in which non-linguistic content is used.

HTML Internationalization Challenges Discussion

Eemeli discussed challenges in improving HTML for internationalization and localization, expressing uncertainty about where to start these conversations. Addison suggested creating a task force or working within specific groups to address these issues. Eemeli mentioned specific examples, including DOM localization and a proposed HTML element for formatted dates and times, which Addison noted has open issues in WHATWG HTML.

JavaScript Internationalization Discussion

The group discussed the need to make JavaScript internationalization capabilities available in HTML, with Addison suggesting that browser implementer buy-in would be necessary for WHATWG consideration. Eemeli agreed to review related links and consider filing issues for TPAC breakout sessions, potentially as joint meetings with WHATWG.

Received on Friday, 26 September 2025 00:53:52 UTC