Open ritikmmathur opened 2 years ago
Hi @ritikmmathur!
I believe e
isn't supported by the version of messageformat we're using under the hoods in globalize. I suggest: (a) checking if latest messageformat supports it, and in case it does (b) bumping up the dependency here --- that's easier said than done since globalize doesn't simply use npm dependency, but a custom way to embed it.
In the meantime, some observations. The e
pattern is a deprecated synonym for ‘c’.
which in turn is compact decimal exponent value: exponent of the power of 10 used in compact decimal formatting
according to https://www.unicode.org/reports/tr35/tr35-numbers.html#Plural_Operand_Meanings. In case plural isn't being used for such case, I believe it's possible to strip this data out from your CLDR usage safely and have globalize working just fine.
I'd happily accept a PR in case you choose the update above (or any other solution). Thanks
globalize has dependency on make-plural package. In latest version i see they have added support to handle e
pattern code link. After doing initial testing, unit formatter is working with make-plural version make-plural-cli@7.1.0.
Would it be okay if I raise PR to update make-plural dependency ??
Sure and thanks!
@ritikmmathur Where's the corresponding PR? Tried searching the pull requests for your username and came up empty.
Hi All,
For locale,
es
when i am using unitformatter, i am getting internal error.Sample usage:
Error Stack Trace:
In CLDR v27.0.0, plural.json has following data,
where as in v40.0.0 plural.json has following data:
Note: for key
pluralRule-count-many
value hase
Similar error is returned for
fr
locale.Please suggest a way to resolve this issue. Also, I would be happy to inner-source the fix 😄
Thanks,
Ritika