New issue
Advanced search Search tips

Issue 710833 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

Fix casing for "Recent Tabs" menu entry

Project Member Reported by mard...@chromium.org, Apr 12 2017

Issue description

Menu entry in English for recent tabs should be:
"Recent Tabs"
instead of 
"Recent tabs". 
 
unnamed.png
81.4 KB View Download
Owner: gambard@chromium.org
Status: Assigned (was: Untriaged)
The problem was on the UK translation.
As we were using the desktop translation and it was purposely changed from title case to sentence case, I will make sure iOS get its own translation.
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 12 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b3f6bfc64c3ab48d05200ca4890657150d6529f7

commit b3f6bfc64c3ab48d05200ca4890657150d6529f7
Author: gambard <gambard@chromium.org>
Date: Wed Apr 12 14:04:43 2017

Update Recent Tabs string to title case

This CL adds a meaning field to the "Recent Tabs" string. It allows
disambiguation with the other "Recent Tabs" strings, incorrectly translated.

BUG= 710833 

Review-Url: https://codereview.chromium.org/2810943004
Cr-Commit-Position: refs/heads/master@{#464012}

[modify] https://crrev.com/b3f6bfc64c3ab48d05200ca4890657150d6529f7/ios/chrome/app/strings/ios_strings.grd

Status: Fixed (was: Assigned)
Will be fixed in the next batch of strings translation.
Cc: gambard@chromium.org
 Issue 712636  has been merged into this issue.
Status: Assigned (was: Fixed)
Verified this bug on:

Device : iPhone 6 Plus
iOS Version : 10.3.1
Build : 59.0.3071.82, Beta59.0.3071.90 Beta

Issue is still reproducible for UK translation. Casing issue for 'Recent Tabs' menu entry is not fixed. It's working fine for US translation. Please see the screenshot attached.
Recent Tabs.png
466 KB View Download
Status: Fixed (was: Assigned)
Thanks for the notification! It should be fixed in the next batch of string translation.
I provided a suggestion for the translation team.

Sign in to add a comment