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

Issue 889760 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Short forms of IME names are inconsistent and don't follow standards

Project Member Reported by tranbao...@chromium.org, Sep 27

Issue description

Currently, the VK's "language menu" button and entries inside the language menu show shortnames of the IME names. These are crucial to recognise which IMEs are available, and which IME is active in use.

However there's many problems:
- Many do not seem to follow any standards.
- Many introduce inconsistencies and confusion.
- Many share the same short names, thus indistinguishable.
etc.

Non-exhaustive list of examples:

- Non-standard codes:
Standard English US --> US
US Workman --> WM
US Workman International --> WMI

- Many use two-letter codes, but:
Dutch (Netherlands) --> NLD (not NL)

- Most use language code:
Japanese --> JA (not JP)
Vietnamese --> VI (not VN)
- Some use country code:
Greek --> GR (that's Greece the country; Greek is EL)
Swiss French/German --> CH (that's Switzerland; the languages are de-CH, fr-CH)
Canadian French --> CA (that's Canada; the language is fr-CA)
Belgian French/Dutch --> BE (that's Belgian; the languages are fr-BE, nl-BE)

- Some use shortform in native scripts
Korean --> 한 (not KO)
Google Japanese --> あ (not JA)
Chinese Pinyin --> 拼 (not ZH blah)
- Others do not:
Russian --> RU (not Cyrillic script)
Greek --> GR (not Greek script)
Thai --> TH (not Thai script)
Arabic --> AR (not Arabic script)

- Many clash (indistinguishable; it's crucial to distinguish):
All Vietnamese IMEs --> VI
All Thai IMEs --> TH
All Arabic IMEs --> AR
Both Google Japanese IMEs --> あ
Both Swiss French/German --> CH
Both Belgian French/Dutch --> BE

 
Labels: -Type-Bug Type-Feature
Status: Available (was: Untriaged)
These should also be made consistent with GBoard, if possible
I think this is partly related to crbug.com/890138.

We can reference other designs, but not necessarily follow, as we could come up with a better one.
Sister issue: crbug.com/889763.
Labels: CrOSLanguage-Current

Sign in to add a comment