New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 690331 link

Starred by 1 user
Status: Fixed
Owner:
█ spqc...@chromium.org
Last visit > 30 days ago
Closed: May 2017
Cc:
nyerramilli@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: On changing browser language, 'Writing direction' string in context menu does not get translated to Hindi.

Reported by lpa...@etouch.net, Feb 9 2017 
Chrome Version: 58.0.3007.0 (Official Build) 0e09de60e479fe2ee105fb731b403c729fce3ac1-refs/heads/master@{#449173} (32/64-bit)
OS: Windows (7,8,10)

What steps will reproduce the problem?
1) Launch chrome, go to chrome://settings and click on 'Show Advanced settings'.
2) From 'Language' section, change the browser language to 'Hindi' and restart the browser.
3) In chrome://settings, right click on 'Search settings' textbox and observe the context menu.

'Writing direction' string does not get translated in Hindi.

'Writing direction' string should get translated in Hindi.

This is a Regression issue broken in M-58, will soon update other info
Manual bisect:
Good build: 58.0.3005.2
Bad build: 58.0.3006.0

Note: Issue is not seen on Mac and Linux OS.
Hindi.jpg
97.4 KB View Download

Comment 1 by ranjitkan@chromium.org, Feb 9 2017

Labels: hasbisect-per-revision ReleaseBlock-Stable
Owner: spqc...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue and below are the bisect details for the same:

Good build: 58.0.3005.2
Bad build: 58.0.3006.0

Bisect URL: https://chromium.googlesource.com/chromium/src/+log/2f2e19599e1d1658516378245c256456318392c9..375ddabe9cdc45673e112c5b1b06cc754aa45759

Change Log: https://chromium.googlesource.com/chromium/src/+/375ddabe9cdc45673e112c5b1b06cc754aa45759

@spqchan: Not sure if this could be related to your change, but assigning to you as per result generated from the bisect script. Kindly have a look into it. Please help us to find an owner if not with respect to your change.

Adding release block label, please undo if not the case.

Thanks.!

Comment 2 by sureshkumari@chromium.org, Feb 15 2017 

@spqchan : Gentle ping, request you to please take a look into this issue. 

Thanks.!

Comment 3 by jmukthavaram@chromium.org, Feb 22 2017 

Friendly Ping!!
lpanse@,
Issue working as expected on Windows 7 & 10 using latest chrome Canary-58.0.3019.0. Could you please check the issue on the same & update the thread accordingly.
Thank you!!

Comment 4 by spqc...@chromium.org, Feb 22 2017 

This CL was recently reverted so it is no longer reproducible.

Comment 5 by spqc...@chromium.org, Feb 22 2017

Labels: -ReleaseBlock-Stable
Removing the release block label because it was reverted. I'm planning to try to fix the CL and land it again, but not anytime soon

Comment 6 by sureshkumari@chromium.org, Mar 2 2017 

Friendly ping to get an update on this.

Thanks.

Comment 7 by spqc...@chromium.org, Mar 2 2017 

This issue is no longer reproducible

Comment 8 by krajshree@chromium.org, Mar 20 2017 

lpanse@ - Could you please check this issue on Windows 7 & 10 using latest chrome Canary-59.0.3046.0 and please let us know if this issue can be closed.

Thanks...!!

Comment 9 by spqc...@chromium.org, May 8 2017

Status: Fixed (was: Assigned)

Comment 10 by tapted@chromium.org, May 9 2017 

I suspect this happened simply because the resource id changed to one that hasn't been translated yet. Strings are only sent for translation in bulk, in time for the Beta channel.
►

Sign in to add a comment