Closed
Bug 1215706
Opened 9 years ago
Closed 9 years ago
Localize "New home screen" name
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(blocking-b2g:2.5+)
RESOLVED
WORKSFORME
blocking-b2g | 2.5+ |
People
(Reporter: theo, Unassigned)
References
Details
(Whiteboard: [systemsfe])
Attachments
(2 files)
I've been thinking this was not the final name, but since string freeze is approaching and I don't see anything related in the meta, I'm filling this bug to make sure the final name gets localized before RA.
I'm talking about the name displayed in Settings > Home Screens > Change home screen.
Feel free to dupe/resolve in something is in the pipeline somewhere.
Reporter | ||
Comment 1•9 years ago
|
||
The string has landed in https://bugzilla.mozilla.org/show_bug.cgi?id=1191745#c34 and is available in l10n repo https://gaia-l10n.allizom.org/integration/gaia-central/rev/34d8e4ed3eb1
Status: NEW → RESOLVED
blocking-b2g: 2.5? → ---
Closed: 9 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•9 years ago
|
||
I pushed the new name in French repo: https://hg.mozilla.org/gaia-l10n/fr/rev/8d5dd72043f4
But it didn't work.
On my build I can see the new name for "Legacy home screen", but not the translation for "Default Home Screen".
Reopening the bug, then.
Status: RESOLVED → REOPENED
blocking-b2g: --- → 2.5?
Resolution: DUPLICATE → ---
Updated•9 years ago
|
Whiteboard: [systemsfe]
Comment 3•9 years ago
|
||
Theo, I'm not sure what this bug is here - which bit isn't working, and what can we/I do to help? Is this a home screen bug, or a bug in infrastructure? Or elsewhere?
Flags: needinfo?(tchevalier)
Reporter | ||
Comment 4•9 years ago
|
||
Hi Chris, here’s a screenshot of the issue.
Legacy Home Screen is correctly picking translations from https://hg.mozilla.org/gaia-l10n/fr/file/60cc80b1f4ab/apps/verticalhome/manifest.properties
But the New Home Screen is not picking the translations here: https://hg.mozilla.org/gaia-l10n/fr/file/60cc80b1f4ab/apps/homescreen/manifest.properties
Side note, for most of those strings, you can’t use Accented English or other pseudo-locales to reproduce, only real locale.
Flags: needinfo?(tchevalier)
Comment 5•9 years ago
|
||
It looks like my build is picking up the correct translations. Theo, is this what I should expect?
Flags: needinfo?(tchevalier)
Reporter | ||
Comment 6•9 years ago
|
||
(In reply to Michael Henretty [:mhenretty] from comment #5)
> Created attachment 8676236 [details]
> [screenshot] correct translations?
>
> It looks like my build is picking up the correct translations. Theo, is this
> what I should expect?
Yes, indeed. And now I see the same with the latest build on Aries. Looks like it’s been fixed somewhere else
Flags: needinfo?(tchevalier)
Comment 7•9 years ago
|
||
Well, marking as resolved going on comment #5 and comment #6. Let's reopen if it resurfaces.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → WORKSFORME
Updated•9 years ago
|
blocking-b2g: 2.5? → 2.5+
You need to log in
before you can comment on or make changes to this bug.
Description
•