Which set of digits should be used for Pashto?

[ebraminio]

While explaining different Arabic script languages digits set here, I find out (123456.789).toLocaleString('ps') gives "۱۲۳٬۴۵۶٫۷۸۹" on Firefox and Safari but "123,456.789" on Chrome and MediaWiki seems agree on Chrome decision.

Considering Pashto language is used with Persian on Afghanistan, if Chrome is right about Afghanistan set of digits, (123456.789).toLocaleString('fa-af') should give same result with Pashto on Chrome but it returns same result with Persian.

So which set of digits is used on Afghanistan and which set of mentioned software should be fixed? And can this issue be settled down first on alreq, somehow, so it would help referencing it later on bug trackers?

[shervinafshar]

We plan to have a section on ALReq about which set of numerals should be used for different locales using Arabic script, but for now, I'd recommend relying on what's in CLDR: ps (arabext): http://unicode.org/cldr/trac/browser/trunk/common/main/ps.xml#L775 fa (inherited to fa-af) (arabext): http://unicode.org/cldr/trac/browser/trunk/common/main/fa.xml#L5170 The discrepancies you see in different browsers might be simply bugs or some intended overrides. ↪ Shervin

…

On Thu, Aug 10, 2017 at 1:17 PM, ebraminio ***@***.***> wrote: While explaining different Arabic script languages digits set here <tesseract-ocr/langdata#72 (comment)>, I find out (123456.789).toLocaleString('ps') gives "۱۲۳٬۴۵۶٫۷۸۹" on Firefox and Safari but "123,456.789" on Chrome and MediaWiki <https://ps.wikipedia.org/wiki/Special:Statistics> seems agree on Chrome decision. Considering Pashto language is used with Persian on Afghanistan, if Chrome is right about Afghanistan set of digits, (123456.789).toLocaleString(' fa-af') should give same result with Pashto on Chrome but it returns same result with Persian. So which set of digits is used on Afghanistan and which set of mentioned software should be fixed? And can this issue be settled down first on alreq, somehow, so it would help referencing it later on bug trackers? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#136>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA1dumdyOgtiUakA282XFYq7qUOBK520ks5sW2VzgaJpZM4Oz7ao> .

[ebraminio]

Filed http://crbug.com/754482 against Chrome. Feel free to close this if there is not any immediate plan for adding those or some other places is used for tracking it (or rename this to the intended long plan if you wish). Thanks

[ebraminio]

I no longer see the issue on Chrome, lets close this.

[r12a]

Thanks for raising the issue, @ebraminio !