Closed
Bug 595825
Opened 15 years ago
Closed 8 years ago
Investigate bundling and reading compiled j20n files in L20n.
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: zbraniecki, Assigned: zbraniecki)
References
Details
Out current approach to bundling localization files in L20n bases on the idea of compiling proprietary l20n format into a javascript file (.j20n) which is then bundled and shipped with a product.
When requested, Gecko will load the .j20n file, prepare a context for it, compile it and then execute.
It seems to be possible to actually compile the .j20n file before bundling and ship a compiled .js file which should be faster to read.
My assumption ignores the potential per-platform dependencies and naively assumes that we have all the required API's for loading compiled javascript from chrome:// into context.
This bug is devoted to demystification of those assumptions.
|
Assignee | |
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•