Use pre-processed l10n data if it's available

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
6 years ago
6 years ago

People

(Reporter: Margaret, Assigned: Margaret)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

6 years ago
This is the other half of bug 810448. In l10n.js, we'll want to see if we have pre-processed l10n JSON, and if so use that instead of loading/parsing all the l10n .ini files in JS to load a locale.
(Assignee)

Comment 1

6 years ago
I have a patch here that checks to see if we already have the l10n data in a JS object:
https://github.com/leibovic/gaia/commit/b8264cc4b49ae8d1fae0c35f9de04c2eb76be045

This builds on top of the work jhford has been doing for bug 810448 and fabrice's patch for bug 811540. Testing with those changes, this definitely speeds up l10n load time.

This should be simple to review, but we need to answer some questions about bug 811540, and jhford will need to land the build changes for bug 810448 before this patch would actually be useful.
If what you have of mine is acceptable, I'll start working on getting it landed!
(Assignee)

Comment 3

6 years ago
Now that bug 821691 landed, we don't need to do this.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.