New issue
Advanced search Search tips

Issue 622785 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 603217



Sign in to add a comment

PIN keyboard localization

Project Member Reported by jdufault@chromium.org, Jun 23 2016

Issue description

The PIN keyboard needs to be localized. Specifically:

- The digits need to be locale specific (maybe use [1]?)
- If the user is entering a PIN, text should be LTR, but if they are entering a password, it should be RTL.

A complicating factor here is that the PIN keyboard is used in settings and oobe, which use different localization methods. Settings uses $i18n[2], and oobe uses i18n-content/i18n-values. Looking at the code, oobe_ui sets the localized strings using web_ui_data_source[3], which looks[4] like it might support the $i18n syntax.

So we might get lucky and both oobe and settings may support the $18n syntax. The localized strings need to be added to both oobe[5] and to settings[6].

1: https://cs.chromium.org/chromium/src/base/i18n/number_formatting.h?l=17
2: https://cs.chromium.org/chromium/src/ui/base/template_expressions.h?l=25
3: https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/chromeos/login/oobe_ui.cc?l=120
4: https://cs.chromium.org/chromium/src/content/browser/webui/web_ui_data_source_impl.cc?l=244
5: https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/chromeos/login/signin_screen_handler.cc?l=367
6: https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/settings/md_settings_localized_strings_provider.cc
 
Status: Started (was: Assigned)
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 3 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Fixed (was: Started)

Sign in to add a comment