Issue metadata
Sign in to add a comment
|
TalkBack uses the TTS of the original language after it's translated |
||||||||||||||||||||||
Issue descriptionChrome Version: M64 OS: Android What steps will reproduce the problem? (1) Enable TalkBack (2) Visit any page that would trigger translate infobar (3) Translate the page What is the expected result? TalkBack should announce the content in the correct TTS system (target language). What happens instead? TalkBack uses the source language for TTS. For example, if I visit a Japanese Wikipedia page, and translate that to English, the pronunciation sounds like Katakana. If it is translated to Chinese, it sounds like Kanji, not the correct Chinese pronunciation. Does this has anything to do with the new neuron on-demand translation system? I'm not sure how this behaves on the old system. Could be a regression.
,
Oct 23 2017
Could some one from localization team, please look into the issue and provide an update.
,
Oct 23 2017
+ibobra
,
Oct 24 2017
,
Oct 27 2017
Hi All, This is not a localization case, it is more on Engineering side. We will forwarding this to Engineering Team for review. Kind Regards, Marvin
,
Nov 29 2017
,
Dec 18 2017
,
Mar 7 2018
,
Dec 7
,
Dec 8
+dmazzoni@ - this is showing as in UI>Browser> because it's the parent of the translate component, but this seems like an issue interacting with web contents so it seems like it should be on the accessibility team's chase list for GAR compliance. What do yo think?
,
Dec 10
Removing other components for now, but @anthonyvd, what do you think? Is this something you can fix or should we work on it? +chrishall
,
Dec 10
If your team has cycles, Dominic, we'd be grateful if you took this on
,
Dec 10
Chris, this looks up your alley |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wychen@chromium.org
, Oct 18 2017