-
Notifications
You must be signed in to change notification settings - Fork 431
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
[IT DateTimeV2] Fix for time expression [minutes] minuti alle [hour] #3067
Conversation
…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
931fc18
to
f668e5c
Compare
@andrew-gradinari Thanks for the ping. We'll review them shortly. |
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.
Could you please add a couple examples of the new behaviour at the model level (DateTimeModel.json) too? This is critical to show the final output is correct.
Also, it would be good if you can add other examples using "e|meno" in other scenarios to show no behaviour there was broken with the change. If such examples already exist, please mention it in the PR description.
@tellarin There are some examples using "e|meno": TimeExtractor.jsonRecognizers-Text/Specs/DateTime/Italian/TimeExtractor.json Lines 195 to 324 in b80b58c
TimeParser.jsonRecognizers-Text/Specs/DateTime/Italian/TimeParser.json Lines 444 to 673 in b80b58c
DateTimeModel.jsonRecognizers-Text/Specs/DateTime/Italian/DateTimeModel.json Lines 1470 to 1521 in b80b58c
Anyway, I have added a few more examples to DateTimeModel.json. I would appreciate it if you could take a look. |
Fix for Italian time expressions such as "5 minuti alle quattro".
References: Time in Italian