Closed
Bug 828276
Opened 11 years ago
Closed 10 years ago
[FTE] English in the graphics for notifications
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Firefox OS Graveyard
Gaia::First Time Experience
ARM
Gonk (Firefox OS)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
Details
(Keywords: l12y)
Attachments
(1 file)
16.96 KB,
image/png
|
Details |
1. go to settings -> device info -> more info -> dev -> first run 2. run through the first run experience 3. go through the tutorial til you get to the notification screen Expected: graphics will be in the language/no wording in the graphics... Actual: graphics is in english
Comment 1•11 years ago
|
||
I'm OK with that. It's a mock text message, and even people using a pt-BR phone may have received a text message in English. Most people don't know a John Doe either ;-). If we want to make this localizable, we can do so at a later stage, I think.
Keywords: l12y
We should probably try to fix this if we can. Simple image swap. cc. Victoria
Reporter | ||
Updated•11 years ago
|
Summary: [FTE] English in the grpahics for notifications → [FTE] English in the graphics for notifications
Comment 3•10 years ago
|
||
I'm not sure that creating images per locale is a great choice: it takes time for someone to produce the images, then review them, them put them in Github. On phones, I see only one image that would benefit from localization (I don't consider the one about e.me in step 3 to need localization, but I might be wrong). https://github.com/mozilla-b2g/gaia/blob/master/apps/communications/ftu/css/images/tutorial/4.png I think it would make more sense to create a blank image and position content over it with CSS for step #4. There are English words in Flatfish images (Notifications, Applications) but I don't consider them as an issue either.
Comment 4•10 years ago
|
||
Marking as WONTFIX. We now display locale agnostic videos in FTU (see bug 1019289).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•