Are We Unified Intl Yet?

All work for mozilla::intl

The unicode components are used in a variety of ways across all of the browser. Unifying them will make the internationalization experience in Firefox consistent, mitigate risks for maintaining new web APIs, and allow for experimentation with next generation internationalization tools.

Metabug

Unifying Gecko

In order to lower the maintenance burden, we should ensure all calls to ICU are routed through mozilla::intl. This chart tracks that unification. This does not include SpiderMonkey work.

Metabug

Unifying SpiderMonkey

SpiderMonkey is the most complicated consumer of ICU code, and it has the largest amount of future changes around the Intl API. It's a key part of testing and validating Mozilla's involvement with and validation of ICU4X.

Metabug

Unifying intl/locale

There have been some attempts to unify parts of i18n in Gecko in the past. Consolidate and update these nicely into intl/components to ensure a cohesive unified implementation.

Metabug

Remove .dtd files from browser.xhtml

This is a key clean-up that will help enable multilingual Firefox, and remove .dtd from the startup path.

Files remaining

Are We * Yet is a template site for sharing updates to Mozilla projects.