[EN .NET] Fix Timex to string conversion of english ordinals 11-13 #2896
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `TimexProperty.ToString()` english conversion of DateTime strings returns the wrong ordinal for days 11-13. In English, ordinals 1 through 3 have special suffixes - 1st, 2nd, 3rd - _except_ on 11-13, where the suffixes are 11th, 12th, 13th. Fixes microsoft#2895
tellarin
approved these changes
Mar 12, 2022
Conor-Keaney
pushed a commit
to purecloudlabs/Recognizers-Text
that referenced
this pull request
Mar 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
TimexProperty.ToString()english conversion of DateTime strings returns the wrong ordinal for days 11-13. In English, ordinals 1 through 3 have special suffixes - 1st, 2nd, 3rd - except on 11-13, where the suffixes are 11th, 12th, 13th.Fixes #2895