Closed Bug 823125 Opened 12 years ago Closed 11 years ago

Use tz.properties to localize continents

Categories

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

x86
macOS
defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C4 (2jan on)
blocking-basecamp +

People

(Reporter: willyaranda, Assigned: kaze)

Details

(Keywords: l12y, late-l10n)

Attachments

(2 files)

Attached image Not translated
They are working on Time & Date on Settings but not on FTU
Keywords: l12y
AFAICT, the code uses the tz.properties, but it may not retranslate when switching language in the ftu?

Requesting blocking-basecamp anyway, as this degrades our first-run experience with Portugese and Spanish.
blocking-basecamp: --- → ?
blocking-basecamp: ? → +
Priority: -- → P1
Target Milestone: --- → B2G C4 (2jan on)
Assignee: nobody → fbsc
Stealing.
Assignee: fbsc → kaze
(In reply to Fabien Cazenave [:kaze] from comment #2)
> Stealing.

I can look into this now if this is not your #1 in the queue.
I’m on it, thanks. :-)
Attached file patch proposal
Attachment #698734 - Flags: review?(fernando.campo)
Keywords: late-l10n
Do we really need to change continent to region now? That sounds like a lot of work for the l10n teams at this point.
Yes we reallly need to, per UX request. And I’m afraid we’ll probably come up with new strings regarding the timezone selector again before the end of the week. :-(
Attachment #698734 - Flags: review?(fernando.campo) → review+
https://github.com/mozilla-b2g/gaia/commit/4ca0f399184b5bcdd025cb376633696908430f9a
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Verified fixed in 2013-01-31-07-02-01 pvt nightly b2g18 build
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: