Closed Bug 837800 Opened 11 years ago Closed 11 years ago

[B2G][First Time Experience]Date & Time page: Country field retains the previous language used until a new country is selected, and the city is always in English

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 835744

People

(Reporter: ckreinbring, Assigned: borjasalguero)

Details

(Keywords: late-l10n, reproducible, smoketest, Whiteboard: l10n)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130116073211

Steps to reproduce:

Unagi version: 
Gecko: 2aa2cbcc4e4bc667770eaeaad9c36efeadc1674a
Gaia: b277f372f097c77dd2ec1988a80e458280dda491
Kernal: Dec 5

1. Begin the First Time Experience.  This usually means flashing the device.
2. Select a language other then English.
3. Select Next until the Date & Time page is reached.
4. Observe the appearance of the country and city fields.
5. Select the Change button on the country field, observe the appearance of the listed countries while selecting a country then tap OK.
6. Observe the appearance of the selected country.
7. Select the Change button on the city field, observe the appearance of the listed cities while selecting a city then tap OK.
7. Observe the appearance of the selected city.


Actual results:

The country listed is either missing (leaving the city as GMT) or shown in the previous language instead of the currently selected one.  The city is listed in English no matter which city is selected.


Expected results:

The country and city are shown in the currently selected language.  So will new countries or cities that are selected.
blocking-b2g: --- → tef?
Keywords: smoketest
Summary: [B2G][First Time Experience]Date & Time page: Country field retains the previous language used until a new country is selected, and the city is always in English. → [B2G][First Time Experience]Date & Time page: Country field retains the previous language used until a new country is selected, and the city is always in English
Unagi version: 20130204070201
Reproducible on latest build with a fresh flash:
2013-02-04-12-36-26 pvt nightly b2g18 build
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
Assignee: nobody → fbsc
Whiteboard: l10n → l10n, testrun 4
Whiteboard: l10n, testrun 4 → l10n
Bug 833393 covers the issue of the cities not being translated.
Bug 830782 covers the FTE being in English even though a different language was selected.
Bug 835744 covers the country missing.

I think you'll have to flash the device rather than go with the OTA?

I believe this bug is a duplicate of multiple bugs.
Can we close this bug and mark as dup for the bugs above?  The other open two bugs have been minus'ed.
No opinion on duping, but not a blocker. Thanks for comment 3, Naoki
blocking-b2g: tef? → -
The key question is if all city names in English will be recognizable in the target languages.   Its likely that there might be a few names that have big enough differences in spelling and translation that they might not be recognizable, or atleast they certainly will be annoying to all users that running thought phone set up.

Is there a list of the city names that get shown in the UI somewhere on mxr or other that we can get some native speakers and other locale experienced users to look at to see if there are any names that are quite a bit different in translation?
This bug might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=837468
I think that there are two bugs here, that are covered by comment #3.

1) Bug 835744 covers the country missing.
2) Bug 833393 covers the issue of the cities not being translated.

I don't think we need to block on 2) (for example, for Europe and Spanish countries, just Spain, there is only "Madrid" on the list, which is the same in Spanish than in English)
In LATAM, I see a lot of Argentina/City, which I think it's good and understandable (excepting that some of those cities must have accent, and they don't like "Argentina/Cordoba" --> "Argentina/Córdoba", but also other places like "Caracas", "Mexico City" (lacks accent, should be "México City" or better "México DF").

For 1), I'd say we should block. I think they can be filled using NITZ (maybe? I don't know), but it's really bad UX to have the Continent empty and the GMT selected. At least, a city is more correct, use somewhere in GMT, like London.

Nominating as tef? again
blocking-b2g: - → tef?
Note: The root cause is also pointed out in Comment 7 that there's no way to currently translate the city names without change in the front end.  Thanks mlevin.

There's a lot more work than just changing the names to being translated.

It seems that people agree that this bug is a duplicate.  Guillermo believes that for 1, we should block.  To note, when you press on the date/time, the continent and city will be filled.  I am closing this off as a duplicate, and noming the bug 835744.

I believe we should separate these bugs out.
Status: NEW → RESOLVED
blocking-b2g: tef? → ---
Closed: 11 years ago
Resolution: --- → DUPLICATE
To note there's already a patch in bug 835744.

Since they are separate issues and require separate work, I think it's better to duplicate this bug.
Verified as duplicate of 835744.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.