Closed
Bug 991573
Opened 11 years ago
Closed 11 years ago
Change success message for Call Barring and Call Waiting interrogation through MMI
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
2.1 S2 (15aug)
People
(Reporter: brg, Assigned: davidg)
References
Details
(Whiteboard: [planned-sprint])
Attachments
(1 file)
This is a suggestion of strings improvement in English that provide information through MMI codes about the status of call barring service.
This is not a blocker in 1.3 but a nice improvement for the future if you agree.
1) Interrogation (*#33#)
1.A) If call barring is currently enabled:
Current English translation: Service was enabled for:
Expected English translation: Service is enabled for:
1.B) If call barring is currently disabled:
Current English translation: Service has been disabled
Expected English translation: Service is disabled
Comment 1•11 years ago
|
||
Moving over to fx os, this might be good input for the copy review.
Component: Other → Gaia
Product: Mozilla Localizations → Firefox OS
Summary: [l10n] Wrong translation in Call Barring service through MMI → Copy improvements in Call Barring service through MMI
Comment 2•11 years ago
|
||
Hi,
I was talking with Beatriz and the problem is that there is a single en-US string for two different actions here:
1) Query the operator what is the status of Call barring
2) Query the operator to CHANGE the status of Call barring
In both cases, if the service end up being deactivated, the English string is "Service has been disabled".
So, with my bad English, I think case 1) should something like "Service is disabled" and case 2) "Service has been disabled".
I don't know, but maybe it is the same for the enabled call barring status.
Comment 3•11 years ago
|
||
(BTW, the reference URL in transvision: http://transvision.mozfr.org/?recherche=Service+has+been+disabled&repo=gaia&sourcelocale=en-US&locale=es&search_type=strings)
Comment 4•11 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #1)
> Moving over to fx os, this might be good input for the copy review.
Thanks, Alex. Also CCing Stephany as she is leading the copy audit.
At a quick look, the proposal in comment 2 looks about right.
Reporter | ||
Comment 5•11 years ago
|
||
Stephany, per comment 4, is there any chance that this change could be included in 2.0?
Flags: needinfo?(swilkes)
Comment 6•11 years ago
|
||
We are well past string freeze so likely not, unfortunately.
Flags: needinfo?(swilkes)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → david.garciaparedes
Assignee | ||
Comment 7•11 years ago
|
||
Because the mmiResponse is exactly the same when you query and when you activate/deactivate the service, I'm passing the original mmi command to success handler, to be able to show one message or the other.
I was trying to include test, but the only thing to test is what text is displayed, and I'm not sure that kind of test makes sense.
Attachment #8462467 -
Flags: review?(etienne)
Comment 8•11 years ago
|
||
Comment on attachment 8462467 [details] [review]
github PR
redirecting...
Attachment #8462467 -
Flags: review?(etienne) → review?(anthony)
Comment 9•11 years ago
|
||
Comment on attachment 8462467 [details] [review]
github PR
Re-redirecting to Doug. Doug: If you have doubts about MMI behaviours, please ask.
Attachment #8462467 -
Flags: review?(anthony) → review?(drs+bugzilla)
Comment 10•11 years ago
|
||
Comment on attachment 8462467 [details] [review]
github PR
I left some comments on the PR. This does need some tests to check that it displays the correct strings. I may have more significant changes after I talk with Gabriele and Anthony about this.
Attachment #8462467 -
Flags: review?(drs+bugzilla) → review-
Comment 11•11 years ago
|
||
Moving this to the right component and marking it as assigned since work is undergoing already.
Status: NEW → ASSIGNED
Component: Gaia → Gaia::Dialer
Updated•11 years ago
|
Whiteboard: [planned-sprint]
Target Milestone: --- → 2.1 S2 (15aug)
Assignee | ||
Comment 12•11 years ago
|
||
Comment on attachment 8462467 [details] [review]
github PR
Sorted comments from Gsvelto and Doug.
Added some tests
Attachment #8462467 -
Flags: review- → review?(drs+bugzilla)
Comment 13•11 years ago
|
||
Comment on attachment 8462467 [details] [review]
github PR
I left some comments on the PR.
Also, this could use a demo.
Attachment #8462467 -
Flags: review?(drs+bugzilla) → review-
Assignee | ||
Updated•11 years ago
|
Attachment #8462467 -
Flags: review- → review?(drs+bugzilla)
Comment 14•11 years ago
|
||
Comment on attachment 8462467 [details] [review]
github PR
Please refer to bug 1049651 in the TODO comment and then I think we're good to go.
Attachment #8462467 -
Flags: review?(drs+bugzilla) → review+
Comment 15•11 years ago
|
||
Also, please update the title of this bug and the PR to better reflect what changes are actually being made.
Assignee | ||
Updated•11 years ago
|
Summary: Copy improvements in Call Barring service through MMI → Change success message for Call Barring and Call Waiting interrogation through MMI
Comment 16•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 17•11 years ago
|
||
Tested and working
Flame
2.1
Gecko-ca5d875
Gaia-fee004d
If call barring is currently enabled and I ask to device status:
Service is enabled for: ...
If call barring is currently disabled and I ask to device status:
Service is disabled
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•