Closed Bug 831583 Opened 12 years ago Closed 12 years ago

[B2G][Portuguese][Maps] The Maps Welcome screen is not translated when the user has set the language to Portuguese.

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:tef+)

VERIFIED WORKSFORME
blocking-b2g tef+

People

(Reporter: jzimbrick, Assigned: andy.tjin)

Details

(Keywords: l12y, Whiteboard: [NPOTB])

Attachments

(1 file)

Repro Steps: 1. Update device to build 20130116070204. 2. Set language to Portuguese. 3. Launch the Maps app for the first time (may need to flash phone). 4. Observe that the Maps Welcome screen is not translated in to Portuguese, displaying fully in English. Actual Results: Maps app Welcome screen is displayed in English, despite the user setting language to Portuguese. Expected Results: Maps app Welcome screen is displayed in Portuguese when the user has set the language to Portuguese. Notes: Found on an Unagi device.
We're not doing the localization of the maps app at mozilla, but we're tracking this in bug 828337.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Unagi, build ID 20130211070202 Verified, that this bug is a duplicate of bug 828337
Status: RESOLVED → VERIFIED
Un-duping this from 828337 and treating as a separate smaller bug. This bug is just about providing translations for the Welcome screen. I'm suggesting this should block because the user is required to accept a disclaimer in order to proceed to main application.
Assignee: nobody → andy.tjin
Status: VERIFIED → REOPENED
blocking-b2g: --- → tef?
Resolution: DUPLICATE → ---
blocking-b2g: tef? → tef+
Whiteboard: [NPOTB]
How are things going here, Andy?
Flags: needinfo?(andy.tjin)
Whiteboard: [NPOTB] → [NPOTB][target 28/2]
Removed [target 28/2] because [NPOTB] is set
Whiteboard: [NPOTB][target 28/2] → [NPOTB]
I spoke with Leo from Nokia and he told me that they completed a release last Friday (Feb 22) that should have this fixed. Do we have this release?
(In reply to Andrew Overholt [:overholt] from comment #6) > I spoke with Leo from Nokia and he told me that they completed a release > last Friday (Feb 22) that should have this fixed. Do we have this release? Have they uploaded a new version of the maps app to marketplace?
Leo told me via email that the latest version should be 1.8.5. I don't see a way to tell what version I have from the phone UI.
(In reply to Andrew Overholt [:overholt] from comment #8) > Leo told me via email that the latest version should be 1.8.5. > > I don't see a way to tell what version I have from the phone UI. You would have inspect the webapps.json file directly. Looking at marketplace (https://marketplace.firefox.com/app/here-maps-packaged), I see the following version number - 1.8.44. Which would imply that they likely do not have the latest bits submitted to marketplace.
You can go to the main menu (top right) and then press 'about'. There you will see the app's version. The latest version will be sent for testing today and hopefully uploaded in the Marketplace asap.
Flags: needinfo?(andy.tjin)
QA - can you test whether or not this reproduces with https://marketplace.firefox.com/app/here-maps-packaged? Latest version is 1.8.55.
Keywords: verifyme
Keywords: verifymeqawanted
Looks good to me; I was able to see the welcome page in Portuguese and Spanish on 1.8.55.
QA Contact: lebedel.delphine
(In reply to AndyT from comment #10) > You can go to the main menu (top right) and then press 'about'. There you > will see the app's version. > > The latest version will be sent for testing today and hopefully uploaded in > the Marketplace asap. Verified fixed from marketplace download, in per comment 12 and my own testing. HERE Maps: version 1.8.55 Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/af9270e8f205 Gaia a78ebf426840b5ef08c0cc3e437ad30aba3e2528 BuildID 20130318070202 Version 18.0
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Keywords: qawanted
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
(In reply to Tony Chung [:tchung] from comment #13) > (In reply to AndyT from comment #10) > > You can go to the main menu (top right) and then press 'about'. There you > > will see the app's version. > > > > The latest version will be sent for testing today and hopefully uploaded in > > the Marketplace asap. > > Verified fixed from marketplace download, in per comment 12 and my own > testing. > > HERE Maps: version 1.8.55 > Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/af9270e8f205 > Gaia a78ebf426840b5ef08c0cc3e437ad30aba3e2528 > BuildID 20130318070202 > Version 18.0 Take that back, the menus and textboxes are in portuguese, not the welcome screen. that still appears in english. reopening, to investigate more.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
If you flash your phone in Spanish or in Portuguese for example, the welcome screen will not appear translated. Menus and textboxes however are localized, as Tony mentions above in Comment 14. To get a localized Welcome Screen, you must uninstall Here Maps and then go to Marketplace and install it again. Otherwise it will not appear localized on first run, even if you have chosen a different locale than English during FTE. Asking more info from AndyT, to what the appropriate behavior should be
Flags: needinfo?(andy.tjin)
(In reply to delphine from comment #15) > To get a localized Welcome Screen, you must uninstall Here Maps and then go > to Marketplace and install it again. > Otherwise it will not appear localized on first run, even if you have chosen > a different locale than English during FTE. > > Asking more info from AndyT, to what the appropriate behavior should be That behavior is known and logged as bug 828337. The localization is done when the app is launched for the first time. So to see the translated Welcome screen, you need to set the system language first and then launch Maps for the first time. Then to verify for a new language, you must uninstall and change language, then re-install from Marketplace and launch again.
Flags: needinfo?(andy.tjin)
(In reply to Dylan Oliver [:doliver] from comment #16) > The localization is done when the app is launched for the first time. So to > see the translated Welcome screen, you need to set the system language first > and then launch Maps for the first time. Then to verify for a new language, > you must uninstall and change language, then re-install from Marketplace and > launch again. I think you may have misunderstood my comment 15: I flashed my phone fresh in Spanish, and also in Portuguese, and in both cases the Welcome screen was *not* localized on first launch. You say that "to see the translated Welcome screen, you need to set the system language first and then launch Maps for the first time.". This is not the case.
(Unless you mean that to see the translated Welcome screen, you need to set the language from the phone's Settings first, and not from FTE screen...)
delphine, please check your version number of Maps (go to top menu, then About). Your preinstalled version is most probably 1.8.44 where it should be 1.8.55. Although we fixed this bug, it will only appear in the preinstalled version if you really preinstall it.
Ok so given all these details, I'll close the bug up again. This is very confusing, but since this is supposed to be the appropriate behavior for now and tracked in Bug 828337, closing up the bug again.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Flags: in-moztrap-
issue is still reproducible on both V1.0.1 and V1.1.0 - This is appropriate behavior though. Verifying issue as fixed. Per Comment 20 tested on Unagi running the following builds: V1.0.1 Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/ccec751a468e Gaia ee0bef61c0a25c806dd1eec5a4e047bc418a5f73 Build 2013-04-02-070202 V1.1.0 Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/68c8a883cfc0 Gaia 1c38c91bb16f2bf0d5066c4787d2249463f61bb3 Build 2013-04-02-070204Maps app Welcome screen is displayed in English, despite the user setting language to Portuguese.Again this is correct behavior.
Status: RESOLVED → VERIFIED
is there anything to uplift here?
Nothing to uplift here. The change was made in the app and submitted to Marketplace. Maybe should be resolved WFM to avoid confusion?
I agree, this sounds more like WORKSFORME than FIXED.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: