Issue metadata
Sign in to add a comment
|
Regression: Text in chrome://settings does not translate to Hindi.
Reported by
vvishwak...@etouch.net,
May 24 2016
|
||||||||||||||||||||||
Issue descriptionVersion: 52.0.2743.3 (Official Build) 8be70850ebcd3ec9433ba7606521c44009e96655-refs/branch-heads/2743@{#23} (32/64-bit) OS: Windows (7,8,8.1,10) What steps will reproduce the problem? 1) Launch chrome, go to chrome://settings and click on Show advanced settings link. 2) From Language section, change the browser language to Hindi and restart the browser. 3) Again go to chrome://settings, click on Show advanced settings button and observe text for second checkbox. Second option does not translate to Hindi. Second option should translate to Hindi. This is a Regression issue broken in M-52, below is the bisect info Manual bisect Good build: 52.0.2740.0 Bad build: 52.0.2741.0 Narrow bisect URL: https://chromium.googlesource.com/chromium/src/+log/580ba30eac72aa1c0bf2b93d31a0843211deba92..b1dcc9b1e28e6de16347ca3e183efb847db50f80?pretty=fuller&n=10000 Suspecting: r394357 ? Note: Issue is not seen on Mac and Linux OS.
,
May 25 2016
This is not a translate problem but a localization problem. https://codereview.chromium.org/1971443003 seems related. +dschuyler PTAL
,
May 30 2016
Not seeing the issue on Canary 53.0.2751.0 , though its still seen on latest M52 branch 52.0.2743.17. dschuyler@ : Could you please take a look into this.
,
Jun 1 2016
dschuyler@ : Gentle ping.
,
Jun 1 2016
this string changed here: https://codereview.chromium.org/1987993002 just give it a while to get re-translated. i would not check translations in developer-y channels
,
Jun 1 2016
laforge@ is it possible we missed a cut-off point for the strings? I'm wondering if this will correct itself once a new set of strings are pulled in.
,
Jun 1 2016
Marking WontFix because I believe this is working as intended. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ashej...@chromium.org
, May 24 2016