After the landing of #35789 I noticed that there are hardcoded English strings in Servo itself. This is likely not exhaustive, but the <input> element actually relies on a few strings:

and

I also introduced some English hardcoding in the about:memory page.

Instead we need to chose a i18n / l10n framework to make it possible to properly localize Servo itself - embedders may use the same solution or not.

Gecko & Firefox use Fluent (https://projectfluent.org/) which has implementations available both for Rust and Javascript. I'm not sure if there are other solutions that would fit our needs.

We should:

1. Agree on which framework to use.
2. Expose the l10n bundles to Rust code, both in main and content processes (shared memory?).
3. Expose the l10n bundles to Servo internal pages (either through a chrome://locale/ path or a new locale:// protocol?)
4. Update all the hardcoded strings
5. Get community help to provide other languages