Normative: Update Table 4 Numbering systems - #438

Would be good to get sign-off from the browser vendors.

@jswalden @litherum

@rkirsling - Could you comment about this since you are working on JSC .

The list I proposed here (except "diak" and "segment") are ALREADY supported by two browser engines already:

• Safari version 13.1
• Chrome / v8 m81

"diak" and "segment" are new in CLDR / ICU and Chrome will support them in m84 with the update to ICU 67.1 .

Sounds good to me. JSC is aiming to defer to ICU / CLDR directly as much as possible, even if our pace of updating is slower than than V8's (...on most platforms, due to reliance on system ICU).

Let's bring this up for the meeting this week.

This has ECMA-402 consensus. We would like to see a more regular process of updating this list, but that doesn't block the current PR. We need to achieve TC39 consensus before it can be merged.

So we don't expect any compatibility issues with other software (#437 (comment))?

Is this PR considered editorial or normative? Is it normative because conforming implementations could become non-conforming based on this PR, or is it editorial because it reflects web reality?

Is this PR considered editorial or normative? Is it normative because conforming implementations could become non-conforming based on this PR, or is it editorial because it reflects web reality?

It is normative because https://ecma-international.org/ecma-402/#sec-partitionnumberpattern stated in step 8.e.iii.3
"If the numberFormat.[[NumberingSystem]] matches one of the values in the "Numbering System" column of Table 3 below, then"

So.. TC39 reach consensus this morning. @sffc @leobalter @gibson042 could you approve?