Closed Bug 858129 Opened 11 years ago Closed 11 years ago

Manual network selection UI is in English (no matter the language configured)

Categories

(Firefox OS Graveyard :: Gaia, defect, P2)

x86_64
Windows 7
defect

Tracking

(blocking-b2g:leo+)

RESOLVED DUPLICATE of bug 859555
blocking-b2g leo+

People

(Reporter: dpalomino, Assigned: kaze)

References

Details

(Keywords: l12y, late-l10n, Whiteboard: IOT, Spain, Ikura, Chile, khepera_43317)

Attachments

(1 file)

Issue seen with Ikura, during certification in Spain. 

gecko commit: b5183c99228bdc5be33340e359efd1b4f0859e92 
gaia commit: 577d13088ebdbd353d13910d3317e713a140415b

When trying to manually select a carrier network, following tags appear in English (with the device being set up to Spanish). 
- Current network (i.e. "current")
- Forbidden network (i.e. "forbidden")

In Spanish should be (something like):
- current > "Actual" or "Red actual"
- forbidden > "Prohibida" or "Red prohibida"

We think this gives a bad impression to the user. However, we are not nominating this as we think this is not blocking. 

See attached pic for details. 

Adding meta cert for Spain dependency. 

Thanks!
David
Sorry, I forgot to include one tag. There will be: 

- current > "Actual" or "Red actual"
- forbidden > "Prohibida" or "Red prohibida"
- available > "Disponible" or "Red disponible"
CC'ed folks, do you know where could be the problem? I can't see the string on the settings app :S
No idea, but I can still reproduce it
Priority: -- → P2
I bet the strings are those of http://mxr.mozilla.org/mozilla-central/source/dom/network/interfaces/nsIDOMMobileConnection.idl#426.

If we'd want to localize those, we probably want a mapping of those. Not sure about other literal values on that interface.
(In reply to Axel Hecht (pto - April 2) [:Pike] from comment #4)
> I bet the strings are those of
> http://mxr.mozilla.org/mozilla-central/source/dom/network/interfaces/
> nsIDOMMobileConnection.idl#426.
> 

I would not bet against it :) 

> If we'd want to localize those, we probably want a mapping of those. Not
> sure about other literal values on that interface.

Yes, we need to localize those, but as David says in the bug description, it seems this is not going to block v1.0.1 release if we can commit to fix this in v1.1 timeframe.
Keywords: l12y
It seems that it's accepted to include this fix in 1.1.
That's the same as bug 845002.
Whiteboard: IOT, Spain, Ikura
blocking-b2g: --- → tef?
Whiteboard: IOT, Spain, Ikura → IOT, Spain, Ikura, Chile, khepera_43317
Tagging late-l10n, as this requires new strings. We don't expect to localize those in an April timeframe at this point.
Keywords: late-l10n
Assignee: nobody → kaze
blocking-b2g: tef? → leo+
I'm resolving this as DUPE of bug 859555, which has a patch. It also has the same b2g flags (leo+), so we're not loosing anything.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
this issue has been reported again on FFOS 1.1 during the Latam Certification

Built ID 20130823171628
Device: Ikura
QC RIL version: "ro.build.firmware_revision=V1.01.00.01.019.180"
gaia commit: 4916f82 Merge branch 'zte/ics_strawberry_cdr' of ssh://10.67.16.41:29418/quic/lf/releases/gaia into ics_strawberry_cdr
gecko commit: a1c2bb0 ZRL modify ACCEPT Http head for MMS
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: