Skip to content

NodeJS and unsupported old locales for plural rules? #379

@sven-oly

Description

@sven-oly

NodeJS version 76 gives 436 failures in plural rules. Of these, 216 are reported for compact sample numbers, e.g., "1c6", which is the same as ICU4C and ICU4J.

However, the other 220 of them are for old locales including "in", "sh", "tl", "iw", "mo", etc. In each case, the results give the actual supported language tags as shown below for "in" (Indonesian) which has the modern tag "id".

{"test_type": "plural_rules", "locale":"in","label":"104","type":"cardinal","plural_type":"cardinal","sample":"0.0","hexhash":"3b059d08c3a377bacba90611a5fa967a7fcf5951"}
--->
{"test_type": "plural_rules", "unsupported_locale":"in","supported_locals":["id"],"test_options":{"type":"cardinal"}}

My question: should we use the actual supported locale when it is found?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions