New issue
Advanced search Search tips

Issue 831387 link

Starred by 9 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Feature

Blocking:
issue 806043



Sign in to add a comment

Consider adding more locale data for Ecma 402 support (Number/DateTimeFormat)

Project Member Reported by js...@chromium.org, Apr 10 2018

Issue description

Chrome's ICU data does not have locale data for languages to which Chrome is not localized. 

With Ecma 402 (EcmaScript Intl API) widely available, a lot of people expect their languages to be supported in the API even though Chrome is not localized to it. 

Firefox bundles most of the locale data. If we just include what's necessary for NumberFormat and DateTimeFormat for at least all the national languages, the data size increase wouldn't be large. 


 
Labels: -Type-Bug Type-Feature
Status: Available (was: Untriaged)
My impression is that this is one of the most frequently reported bug for Intl. It'd be great to have it addressed, if it doesn't increase download size much.
This is a bug that I would really love to see fixed.

I agree that a wide language support is expected by most developers, and since Firefox, Safari, Edge and IE seem to support more languages, this bug really reduces the value of the Intl api for those of us who have to work with a language not supported by Chrome.

Sign in to add a comment