Closed
Bug 595817
Opened 15 years ago
Closed 8 years ago
Migrate toolkit&browser from .dtd/.properties to l20n
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: zbraniecki, Assigned: zbraniecki)
References
Details
Attachments
(1 file)
276.96 KB,
patch
|
Details | Diff | Splinter Review |
Initially, we need to create a set of tools for migrating XUL/JS/XBL code from old architecture to the new one.
It requires tools for automating as much of the migration as possible and regression tests. It will also require a lot of hand work.
Assignee | ||
Updated•15 years ago
|
Assignee | ||
Comment 1•15 years ago
|
||
this patch migrates firefox 4.0beta4 (rev 7c19fb706708) to l20n. I used it for performance measurements
Assignee | ||
Comment 2•15 years ago
|
||
silme (http://hg.mozilla.org/l10n/silme) and silme-apps (http://hg.mozilla.org/users/zbraniecki_mozilla.com/silme-apps/) gained a lot of features for L20n/J20n conversion and testing.
In particular, regression testing is being done via:
- dtd -> inline
- l20n -> inline
- compare two inlines.
Assignee | ||
Comment 3•8 years ago
|
||
Seven years later, we're making another attempt to refactor our l10n layer.
The new tracking bug is bug 1365426 and I'll mark the previous effort as "INCOMPLETE".
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•