Internationalization Working Group Teleconference - 16 October 2025

https://www.w3.org/2025/10/16-i18n-minutes.html

Here is the meeting summary:

Quick recap

The WG reviewed several technical proposals and updates related to HTML formatting, Google participation, and automation of TC39 repos, including discussions about internationalization and language tags. The group also reviewed the internationalization glossary document, deciding to classify terms as normative or non-normative and implement visual distinctions for better organization.

Next steps

Addison to follow up with Shane about adding W3C prefixed labels to TC39 repos.
Addison to continue following up with Google for participation.
Eemeli to draft the errata for IRI RFC 3987 regarding isolates and email it to Addison, John, and Martin.
xfq to think about next steps for the glossary normativity work and report back to the group.

Summary

TPAC Proposals and ECMAScript Updates

The team discussed several agenda items, including updates on HTML article formatting, Google participation, and automation of TC39 repos. Eemeli shared progress on two TPAC breakout session proposals related to internationalization, which need to be submitted by next Wednesday. The team reviewed ECMAScript proposal 402 regarding integer number format and plural rules, with Addison providing a positive review. They also discussed a new incoming issue (2039) from Web Extensions regarding APIs for managing the accept language header, which Addison flagged as potentially incomplete and in need of further review.

Credential Localization and Language Tags

The group discussed two main topics: verifiable credentials localization and language tags for non-linguistic content. Addison explained the implementation challenges of credential localization, including template matching and defaulting issues. The team agreed to use similar mechanisms to other web localization standards. For language tags, they reviewed a pull request that changed the default value for undetermined languages to "zxx" and made the specification more explicit about non-linguistic content. Addison raised concerns about using "und" as it could have unintended consequences in JavaScript.

Internationalization Glossary Normative Classification

The group discussed how to handle normative and non-normative terms in the internationalization glossary document. Addison explained that while the glossary is currently non-normative, they plan to classify terms as normative or non-normative and eventually move the document to a normative status. The team agreed on using a blue box to visually distinguish normative terms, with Addison noting that machine-readable attributes would also be needed for tooling. They decided to start marking terms as normative and begin editing the definitions to ensure they meet normative requirements, potentially creating a separate branch for this work.

Received on Friday, 17 October 2025 00:27:58 UTC