Closed domi41 closed 4 years ago
I've pushed to my branch some changes that implement the above, hopefully without breaking too much.
One caveat: things like twenty eleven
yield 31
now.
I also pushed some small fixes to the english large number mapping.
That's excellent! I'm not familiar with complex numbers in other languages so I couldn't add them, but I figured the easiest way to do it would be to just provide different parsers for each language like you suggested since they are all different and have different edge cases. I'm pretty busy right now, but will take a look when I have a chance. Thanks!
Merged in #5
Hello !
Support for french won't be as easy as replacing the mapping.
I've added a test-case to my
i18n-french
branch.Here's the excerpt :
How do you feel about ISO639 for language codes ? Perhaps one with the variants, such as
fr_FR
?Any ideas on how to proceed with I18N using custom parsers for each language ?
To enable I18N, we need to:
Be able to run custom code per language