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.
Session goal
Collect comments on the proposal.
Recruit interests to work on the standards development.
Discuss the most appropriate forum for further work.
Additional session chairs (Optional)
No response
IRC channel (Optional)
dom-localization
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
MrHBS
commented
3 months ago
Session 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.
Session goal
Collect comments on the proposal.
Recruit interests to work on the standards development.
Discuss the most appropriate forum for further work.
Additional session chairs (Optional)
No response
IRC channel (Optional)
dom-localization
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
No response
Estimated number of in-person attendees
Don't know (Default)
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)