Closed
Bug 712400
Opened 13 years ago
Closed 13 years ago
Write a script to get all loc(...) strings
Categories
(addons.mozilla.org Graveyard :: Localization, defect, P1)
addons.mozilla.org Graveyard
Localization
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: andy+bugzilla, Unassigned)
References
Details
We've got lots of loc(..) strings because we don't know what the text should be. These will need to be all cleaned up and turned into localizable strings so that the localizers can do their job.
This will need to be done sooner rather than later given the time localizers need.
Updated•13 years ago
|
Priority: -- → P1
Comment 1•13 years ago
|
||
Why would we burden the localizers with a bunch of strings that will probably go away when we get the new mocks for the Market?
Comment 2•13 years ago
|
||
That said, a tool to find all the loc() strings is a good idea anyway.
Reporter | ||
Comment 3•13 years ago
|
||
Yeah its just a script to find all the loc() strings so we don't miss them. I doubt we'll get full mocks with text for every page, so we'll have to get a process in place for checking these then converting them to localizable.
Reporter | ||
Comment 4•13 years ago
|
||
./manage extract_loc
https://github.com/mozilla/zamboni/commit/38c093
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•