[Python][EN DateTimeV2] Fix for case like 'March one 2020' #3099
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
…n for Units (microsoft#2877) (microsoft#2879) - Support informal degrees in PT and ES (microsoft#2877); - Fix issue in generation of Spanish unit resources; - Re-generate all resources across platforms.
…icrosoft#2878) * Enabling SpanishMexican culture in Number/Unit/DateTimveV2 * Update Spanish number specs according to review Co-authored-by: Colm Dillon <[email protected]>
* Add Portuguese DateTime support in Python * Update Specs with Python changes * Fix Number import issue * Update specs according to build and review * Remove empty NotSupported fields from specs
microsoft#2863) (microsoft#2892) Co-authored-by: aitelint <[email protected]>
…eTimeRanges (microsoft#2894) * Workaround for TimexProperty.ToString() to not crash on DateTimeRanges * Add TODO for fixing the TimexProperty date range representation properly according to review
Fetch microsoft/Recognizers-Text upstream changes
[NLU-2858] Fetch upstream changes from microsoft:master -> purecloudlabs:master
Merge MS Recognizers into master
Bringing Pureclould Labs master up to-date with Microsoft master
This reverts commit 22f56fd.
Update fork with MS recognizers latest
Sync Fork
Fetch Upstream fork
andrew-gradinari
changed the title
andrew-gradinari
force-pushed
the
fix-en-date-mdy
branch
from
b2daed5
to
ad136a0
Compare
andrew-gradinari
force-pushed
the
fix-en-date-mdy
branch
from
ad136a0
to
7ed5b55
Compare
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.
Recognizers fails to pick up the year for dates in the format of "Month(text) Day(text) Year(digit)":
April first 2021→2023-04-01/2024-04-01March one 2020→2023-03-01/2024-03-01There is also a problem with the resolved values - PastResolution is in the future when it should be in the past relative to ReferenceDateTime:
{ "Input": "Oct twenty three", "Context": { "ReferenceDateTime": "2023-04-25T00:00:00" }, "Results": [ { "Text": "Oct twenty three", "Type": "date", "Value": { "Timex": "XXXX-10-23", "PastResolution": { "date": "2024-10-23" }, "FutureResolution": { "date": "2023-10-23" } }, "Start": 0, "Length": 16 } ] }