-
Notifications
You must be signed in to change notification settings - Fork 966
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
ToQuantity / Ordinalize / ToOrdinalWords / ToWords should do nothing for unsupported languages. #132
Comments
Thanks for raising this @hazzik. Yeah, we should fix this soon. |
I think this should be fixed by #149; but we need to write some tests to verify and enforce this. |
I'm trying to implement the tests, but I can not decide which culture to use as "unknown" |
Maybe "dc-DummyCulture"?! |
CultureInfo might crap out on that though! ;) |
.NET throws "Unsupported culture" exception. |
I think |
But that's English too, right? I don't know. Give that a shot. If it doesn't work, we can pick a culture with no existing localisation here and push this up. We can deal with that culture later if it ever pops up. |
Not exactly, it has own language code (iv/IVL), but for resources it will select the neutral resource (which is English) |
ah, cool. Thanks. Go for it then :) |
To verify this you could change the Invariant\ToQuantityTests to:
|
This is fixed by #162 |
No description provided.
The text was updated successfully, but these errors were encountered: