-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Table 4: Numbering systems with simple digit mappings #437
Comments
The list I proposed here (except "diak" and "segment") are ALREADY supported by two browser engines already:
"diak" and "segment" are new in CLDR / ICU and Chrome will support them in m84 with the update to ICU 67.1 . |
You can check the browser support these or not by the following html hack
|
I've filed #183 and https://bugzilla.mozilla.org/show_bug.cgi?id=1413504 a while ago, but didn't make further progress on the Firefox bug, because at least at that point of time, there wasn't good font support for these scripts and it didn't seem worthwhile to invest time supporting numbering systems which can't be displayed to the user anyway. As mentioned in #183, https://tc39.es/ecma402/#table-numbering-system-digits is currently limited to numbering systems present in CLDR 21 which can be displayed with Unicode 5 compatible characters. The restriction to Unicode 5 was put in place because that's the Unicode version supported in Windows Vista (https://searchfox.org/mozilla-central/rev/a40ef31fc9af34a99ceda6d65cdc4573d52b83d2/js/src/builtin/intl/NumberFormat.js#570-576). Are there any compatibility concerns with other software when we start requiring to support all non-algorithmic numbering systems provided by CLDR? |
Table 4: Numbering systems with simple digit mappings
https://tc39.es/ecma402/#table-numbering-system-digits
lists "Numbering systems with simple digit mappings" that are easy to implement and mandated to be supported by ECMA402. Newer version of CLDR now include MORE type="numeric". I think we should include them into this table
The text was updated successfully, but these errors were encountered: