Closed
Bug 1005719
Opened 11 years ago
Closed 9 years ago
[B2G][1.4][Settings] The string "Screen reader started" appears in English on all languages
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v1.3 unaffected, b2g-v1.4 affected, b2g-v2.0 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| b2g-v1.3 | --- | unaffected |
| b2g-v1.4 | --- | affected |
| b2g-v2.0 | --- | affected |
People
(Reporter: KTucker, Unassigned)
References
Details
(Whiteboard: LocRun1.4, LocRun2.0-2)
Attachments
(1 file)
|
20.03 KB,
image/png
|
Details |
Description:
The string "Screen reader started" appears in English on all languages.
Repro Steps:
1) Updated Buri to Build ID: 20140430000201
2) Change the language to "French".
3) Tap on the "Settings" app.
4) Tap on "Developer" and tap on "Show accessibility settings".
5) Back out and tap on "Accessibility".
6) Tap on the "Screen reader" toggle.
7) Tap on "Start" and observe the "Screen reader started" message.
Actual:
The string "Screen reader started" is not translated.
Expected:
The string is translated on all languages.
Environmental Variables
Device: Buri v 1.4.0 Mozilla RIL
Build ID: 20140430000201
Gecko: https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/123485e733d5
Gaia: 81e97c3ca58be0487292011bc59efa4cebab30be
Platform Version: 30.0
Firmware Version: v1.2-device.cfg
Notes:
Repro frequency: 100%
See attached: screenshot
| Reporter | ||
Comment 1•11 years ago
|
||
Does this happen on 1.3?
| Reporter | ||
Updated•11 years ago
|
status-b2g-v1.4:
--- → affected
Comment 2•11 years ago
|
||
In 1.3 the option to enable Screen Reader is located in Developer menu, and when enabled, there is no message popping up saying that screen reader is enabled.
In short, this does NOT reproduce in 1.3 (because the message does not exist).
Tested on:
Device: Buri 1.3 MOZ
BuildID: 20140505024001
Gaia: 667539f1ed4becc45b182a5f1046221d3eeb9e7c
Gecko: bf3fe474bf50
Version: 28.0
Firmware Version: v1.2-device.cfg
status-b2g-v1.3:
--- → unaffected
Keywords: qawanted
Comment 3•11 years ago
|
||
Not a blocker mainly because accessibility settings will only be shown if the dev switch is flipped. However, we should get this fixed.
Yura - Can you add this to your backlog of items to fix?
Flags: needinfo?(yzenevich)
Comment 5•11 years ago
|
||
It looks like the sting is localized in most languages (at least french as reported in the description):
http://transvision.mozfr.org/string/?entity=dom/chrome/accessibility/AccessFu.properties:screenReaderStarted&repo=aurora
It looks like m-c (and hence the gecko used in this build) only has en-US, the other locales are packaged differently and not present by default.
Flags: needinfo?(yzenevich)
Comment 6•11 years ago
|
||
(In reply to Yura Zenevich [:yzen] from comment #5)
> It looks like the sting is localized in most languages (at least french as
> reported in the description):
> http://transvision.mozfr.org/string/?entity=dom/chrome/accessibility/
> AccessFu.properties:screenReaderStarted&repo=aurora
I don't think that's enough to ensure that the string is localized in the product. The string needs to be referenced correctly in gaia code in order for it to be localized.
Comment 7•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #6)
> (In reply to Yura Zenevich [:yzen] from comment #5)
> > It looks like the sting is localized in most languages (at least french as
> > reported in the description):
> > http://transvision.mozfr.org/string/?entity=dom/chrome/accessibility/
> > AccessFu.properties:screenReaderStarted&repo=aurora
>
> I don't think that's enough to ensure that the string is localized in the
> product. The string needs to be referenced correctly in gaia code in order
> for it to be localized.
The origin of that string is chrome JS, it has nothing to do with gaia or any content. Pretty sure :)
Comment 8•11 years ago
|
||
(In reply to Eitan Isaacson [:eeejay] from comment #7)
> (In reply to Jason Smith [:jsmith] from comment #6)
> > (In reply to Yura Zenevich [:yzen] from comment #5)
> > > It looks like the sting is localized in most languages (at least french as
> > > reported in the description):
> > > http://transvision.mozfr.org/string/?entity=dom/chrome/accessibility/
> > > AccessFu.properties:screenReaderStarted&repo=aurora
> >
> > I don't think that's enough to ensure that the string is localized in the
> > product. The string needs to be referenced correctly in gaia code in order
> > for it to be localized.
>
> The origin of that string is chrome JS, it has nothing to do with gaia or
> any content. Pretty sure :)
Ok - so why is not localized then?
Comment 9•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #8)
> (In reply to Eitan Isaacson [:eeejay] from comment #7)
> > (In reply to Jason Smith [:jsmith] from comment #6)
> > > (In reply to Yura Zenevich [:yzen] from comment #5)
> > > > It looks like the sting is localized in most languages (at least french as
> > > > reported in the description):
> > > > http://transvision.mozfr.org/string/?entity=dom/chrome/accessibility/
> > > > AccessFu.properties:screenReaderStarted&repo=aurora
> > >
> > > I don't think that's enough to ensure that the string is localized in the
> > > product. The string needs to be referenced correctly in gaia code in order
> > > for it to be localized.
> >
> > The origin of that string is chrome JS, it has nothing to do with gaia or
> > any content. Pretty sure :)
>
> Ok - so why is not localized then?
Possibly because the gecko layer is not localized the same way it is on desktop/android? If that is the case, we will have other issues with the screen reader, since it will use en-US for internal strings regardless of the locale set in gaia.
Comment 10•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #8)
> (In reply to Eitan Isaacson [:eeejay] from comment #7)
> > (In reply to Jason Smith [:jsmith] from comment #6)
> > > (In reply to Yura Zenevich [:yzen] from comment #5)
> > > > It looks like the sting is localized in most languages (at least french as
> > > > reported in the description):
> > > > http://transvision.mozfr.org/string/?entity=dom/chrome/accessibility/
> > > > AccessFu.properties:screenReaderStarted&repo=aurora
> > >
> > > I don't think that's enough to ensure that the string is localized in the
> > > product. The string needs to be referenced correctly in gaia code in order
> > > for it to be localized.
> >
> > The origin of that string is chrome JS, it has nothing to do with gaia or
> > any content. Pretty sure :)
>
> Ok - so why is not localized then?
I confirm, it's not under https://hg.mozilla.org/gaia-l10n/en-US ? Then it's not localized.
Comment 11•11 years ago
|
||
I don't think this bug is actually late-l10n at this point, since it requires a lot more work (we need those strings in Gaia, we don't localize Gecko at the moment).
Updated•11 years ago
|
status-b2g-v2.0:
--- → affected
Whiteboard: LocRun1.4 → LocRun1.4, LocRun2.0-2
Comment 14•9 years ago
|
||
This is not an issue any more. Now if screen reader is enabled, a user is only able to select a language compatible with the screen reader.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(yzenevich)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•