-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localization API #96
Comments
That would be a much better solution to #93, which is more or less a hack. |
It's still not a proper localization because it doesn't translate messages. |
messages? |
A user passing |
Also your code will break when there's no |
those are separate features; a language pack of custom symbols or full form words can be loaded into the instance. providing all variations is something i wouldn't attempt for free. |
Then |
the method has always existed, it just wasn't used in this lib. |
That table only shows the latest verions of browsers. |
|
|
are you grasping what you're suggesting? a language pack for all permutations is unmanageable. as per your claim of support... https://caniuse.com/#feat=internationalization |
Nothing "unmanageable" in that.
As per your claim of support: the link clearly shows that it's not supported in all browsers. |
i don't care if my code breaks in a deprecated browser that only runs in an OS that's 10+ years out dated. I just don't care. I don't care if you want this feature to work on modern browsers and netscape 1.0. You're not paying me money, so I don't care. |
I don't care about what you care and don't care. |
And yet you opened this ticket, and it gets over 4 million installs a week. I don't care if you care or not. I did you a favor. |
I can see that your library supports some localization via
separator
,symbols
andfullforms
.I guess, for Russian it would be something like:
You could make a directory called
locales
where people could submit pull requests with their languages.A similar API:
https://github.com/sindresorhus/pretty-bytes#readme
Notice how they also use
,
in that example.That's because they use
number.toLocaleString()
instead ofseparator
.They should have also checked for
number.toLocaleString
existence before using it and then fall back to a default separator.They also don't have
kB
translated.These are localization API ideas you might want to review in some future if you decide on adding localization to this library.
I don't need localization, I'm using
en-US
.The text was updated successfully, but these errors were encountered: