You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this cool tool, I'm using it to parse some dates in English and that's quite good :)
However I want to help you to increase the translation range but the structure of the project doesn't seem to be adequate to the extensibility required for contributions.
As I see, we have a lot of translatable strings mixed with the functionality... It would be so much better to separate functionality/feature from the string searched/used. Basically making a small dictionary for the functions.
I saw you have - on the experimental_plugins - an english.js which contains some words already.
That'd be nice if you hadn't mixed some functionality (like 'findSentences' and alike).
Last but not least, consider doing a language identification based on the culture, not on the language itself. E.g:
pt_PT !== pt_BR
en_US !== en_UK
and so on.
If you want I can help out, just tell me if you'd like some help on that ;) And thanks for your time!
One thing that would be interesting to check is the possibility to integrate either with a tool/library like FormatJS or with the Unicode Group, more exactly the ICU sub-group ( http://site.icu-project.org/ ).
The text was updated successfully, but these errors were encountered:
Hi @loadfive,
Thanks for this cool tool, I'm using it to parse some dates in English and that's quite good :)
However I want to help you to increase the translation range but the structure of the project doesn't seem to be adequate to the extensibility required for contributions.
As I see, we have a lot of translatable strings mixed with the functionality... It would be so much better to separate functionality/feature from the string searched/used. Basically making a small dictionary for the functions.
I saw you have - on the experimental_plugins - an english.js which contains some words already.
That'd be nice if you hadn't mixed some functionality (like 'findSentences' and alike).
Last but not least, consider doing a language identification based on the culture, not on the language itself. E.g:
pt_PT !== pt_BR
en_US !== en_UK
and so on.
If you want I can help out, just tell me if you'd like some help on that ;) And thanks for your time!
One thing that would be interesting to check is the possibility to integrate either with a tool/library like FormatJS or with the Unicode Group, more exactly the ICU sub-group ( http://site.icu-project.org/ ).
The text was updated successfully, but these errors were encountered: