I created
https://wiki.mozilla.org/L20n/Firefox where I'd like to
document the effort of porting Firefox to L20n. If you're not
familiar with the plan read the blog post [1]. The second part
targeted at Firefox front-end developers is coming this week.
The High Level Status paragraph has a very rough outline of different
areas that we need to cover. I'd like to break each area down into
milestones and I'll need everyone's help doing that.
I've been thinking about the landing strategy and how we've said we
considered the About window. I think you hit the nail on the head
when you put the About window in the first section. That was just a
proof of concept. We proved that all parts of the UI can be localized
with L20n (XUL, XBL, chrome HTML, content HTML). But it's not good
enough to hold the ground after the landing.
Axel and Zibi suggested offline that we pick a Talos measure and stick
to it. I agree. This should be the feature we'll land first too. I
created a l20n-ts-paint branch which is the minimal path that gets us
a single string localized with L20n (the URL bar placeholder). I
talked to Zibi and we think it would be best to convert
browser.{dtd,properties} into browser.ftl (around 1,500 strings to be
parsed in total) and start by localizing the following pieces of the
UI:
- the URL bar placeholder ("Search or enter address"),
- the Search bar placeholder ("Search"),
- the Menu bar labels ("File", "Edit", "View", etc.).
I doubt we'll be able to migrate all of browser.xul. Instead I think
we should factor in the hit we'll be taking from running both the old
and the new l10n solution in parallel. If we can get good perf
results with this, then it's only going to get better once we remove
the old solution.
If everyone agrees, I'll file a bug to get this done!
-stas
[1]
https://blog.mozilla.org/l10n/2016/06/29/l20n-in-firefox-a-summary-for-localizers/
[2]
https://github.com/mozilla/gecko-dev/compare/master...stasm:l20n-ts-paint