Closed
Bug 623339
Opened 14 years ago
Closed 13 years ago
Localize AoA strings
Categories
(support.mozilla.org :: Army of Awesome, task)
support.mozilla.org
Army of Awesome
Tracking
(Not tracked)
VERIFIED
FIXED
2.4.3
People
(Reporter: paulc, Assigned: paulc)
References
Details
We need to make sure all strings on the AoA page are localizable. This bug is just about strings that go to Verbatim.
Comment 1•14 years ago
|
||
We'll be adding some new strings after 2.4.3 for the features that allow flagging tweets and filtering the list. In total it's about 5 strings with 2 words each. Paul, since we know the strings now, can we somehow include them into the string freeze for 2.4.3 so we don't need to do another round of l10n for 2.5? Here's a tentative list of new strings: -"Remove" -"Filter by" -"Recent tweets" -"Unanswered tweets" -"Answered tweets" -"All tweets"
No longer depends on: 624445
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > Paul, since we know the strings now, can we somehow include them into the > string freeze for 2.4.3 so we don't need to do another round of l10n for 2.5? We should just do them when we have the features there too. It can be confusing to translate something that you can't see working or test in any way. Most releases include string changes, so there will probably be some aside from AoA anyway.
Comment 3•14 years ago
|
||
(In reply to comment #2) > We should just do them when we have the features there too. It can be confusing > to translate something that you can't see working or test in any way. This sounds good to me. Thanks
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → paulc
Assignee | ||
Comment 4•13 years ago
|
||
Hopefully this gets all of them! https://github.com/jsocol/kitsune/commit/86090dfb6763b73ecfce4f38bf23ed9d8fedbd0a Please file additional bugs if any strings are found not localizable. Thanks!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
Unable to verify verbatim changes, marking as verified for the 2.4.3 release- please re-open if the issue persists.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•