The Road to Intl.MessageFormat
summary
Proposal brings a standardized message parser into JS as Intl.MessageFormat stage 1 with a parallel resource format (think messages.mf linked from HTML via a l10n-like rel), backed by Unicode CLDR/ICU so browsers can offload parsing and formatting. Firefox already uses Project Fluent; ICU aims an ICU 72 tech preview for the message format. API surfaces include a single-message parser and a resource parser, supports plural/selector rules and number/date formatters, and has no hard message-size limit defined yet.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:28What would be better?
- 10:54STANDARDISE
- 17:15Localising elements, not strings
- 18:45Make it easy to make the right choices
related talks
19mInternationalize your web apps
26mThe State of the Art in Localization
28mFormat data and strings in any language with FormatJS and react-intl
24mClient Side Internationalization
52mIntl Me This, Intl me That
24mINTL: The best browser API you’re not using
19mLost in Translation? Intl, the Rosetta Stone of Web Development
53mIntl is Your Superhero