-
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
Changed OrdinalizeExtensions to better accommodate localisations. #217
Conversation
Added pt-br Ordinalize localisation.
Minor code formatting fixes and cleanup.
Since @thunsaker said Spanish rules are exactly the same, I added Spanish localisation too. Hope I didn't get something wrong. Would be great if someone could validate all these changes. I'll check tomorrow if there are any problems. |
Spanish additions look good, (one inline comment). Thanks for doing it. |
[InlineData("102", "102º")] | ||
[InlineData("103", "103º")] | ||
[InlineData("1001", "1001º")] | ||
public void OrdinalizeString(string number, string ordinalized) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rename this to Ordinalize please
Never mind. I see the reason now.
Thanks @akamud. Great work. Please leave us a comment when the feedback is applied. |
…l Gender for Ordinalizer. Fixed some typos and code clean-up.
Please check if everything is correct now. I'll be back home tonight if there's still something wrong. |
Thank you for making them @MehdiK, I wouldn't be able to fix them until later tonight. |
Thanks for the contribution. This is now available on NuGet as v1.23.1. |
Added pt-br Ordinalize localisation.