DOM Localization
- Past
- Confirmed
- Breakout Sessions
- Past
- Confirmed
- Breakout Sessions
Meeting
The base requirements for message formatting and localization are experiencing some significant advancements as the MessageFormat 2 spec is being defined in the Unicode Consortium, and the Intl.MessageFormat API is being defined in TC-39 for JavaScript.
Building on these, work should start on defining a localization system for HTML that's reactive rather than imperative, and which allows for localization without any JS dependency. At Mozilla, we've been using a similar system based on Fluent to localize Firefox and our other projects, and have learned much about what works and what doesn't. Some of our ideas have been collected as a draft of what this could look like in practice.
Agenda
Chairs:
Eemeli Aro
Description:
The base requirements for message formatting and localization are experiencing some significant advancements as the MessageFormat 2 spec is being defined in the Unicode Consortium, and the Intl.MessageFormat API is being defined in TC-39 for JavaScript.
Building on these, work should start on defining a localization system for HTML that's reactive rather than imperative, and which allows for localization without any JS dependency. At Mozilla, we've been using a similar system based on Fluent to localize Firefox and our other projects, and have learned much about what works and what doesn't. Some of our ideas have been collected as a draft of what this could look like in practice.
Goal(s):
-
Collect comments on the proposal.
-
Recruit interests to work on the standards development.
-
Discuss the most appropriate forum for further work.
Materials:
Minutes
Read minutesExport options
Personal Links
Please log in to export this event with all the information you have access to.
Public Links
The following links do not contain any sensitive information and can be shared publicly.