Closed
Bug 824714
Opened 12 years ago
Closed 12 years ago
wrong l10n IDs in the Dialer
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)
Tracking
(blocking-basecamp:+)
People
(Reporter: kaze, Assigned: kaze)
References
Details
(Keywords: late-l10n, regression)
Attachments
(1 file, 1 obsolete file)
1.69 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
Regression caused by bug 817988:
https://github.com/mozilla-b2g/gaia/commit/60aac2d#diff-3
Here’s a quick fix.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → kaze
Assignee | ||
Updated•12 years ago
|
Attachment #695756 -
Flags: review?(etienne)
Assignee | ||
Comment 1•12 years ago
|
||
Requesting BB+ status: l10n + follow-up of a BB+ bug.
Comment 2•12 years ago
|
||
What's the regression? (excepts introducing late-l10n keys)
If we can't have the strings I'd rather have no l10n-ids for those buttons than false ones...
Assignee | ||
Comment 3•12 years ago
|
||
Étienne, the regression is that two data-l10n-id have changed for no reason…
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P2
Target Milestone: --- → B2G C4 (2jan on)
Comment 4•12 years ago
|
||
(In reply to Fabien Cazenave [:kaze] from comment #3)
> Étienne, the regression is that two data-l10n-id have changed for no reason…
I'm sorry something as lame as
|camera-a11y-button.aria-label=Hang Up|
got merged in the first place.
But let's not build on top of this mess and correct the keys.
Assignee | ||
Comment 5•12 years ago
|
||
OK, then it’s a late-l10n fix.
Attachment #695756 -
Attachment is obsolete: true
Attachment #695756 -
Flags: review?(etienne)
Attachment #695763 -
Flags: review?(stas)
Assignee | ||
Updated•12 years ago
|
Status: NEW → ASSIGNED
Comment 6•12 years ago
|
||
Comment on attachment 695763 [details] [diff] [review]
l10n fix
A lot of new strings is coming for e.me. Let's land that too.
Attachment #695763 -
Flags: review?(stas) → review+
Comment 7•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•