Skip to content

Conversation

@andrew-gradinari
Copy link
Contributor

Fix and testing for invalid dates for German.

Details

Invalid dates like "32.04.2023" are being resolved incorrectly:

{
  "text": "2.04.",
  "type_name": "datetimeV2.date",
  "start": 1,
  "end": 5,
  "resolution": {
    "values": [
      {
        "timex": "XXXX-04-02",
        "type": "date",
        "value": "2023-04-02"
      },
      {
        "timex": "XXXX-04-02",
        "type": "date",
        "value": "2024-04-02"
      }
    ]
  }
}

tellarin and others added 21 commits March 25, 2022 16:35
…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 <cdillon@ip-192-168-0-108.ec2.internal>
* 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 <Fabrizio.Sorba@telusinternational.com>
…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
Update fork with MS recognizers latest
@andrew-gradinari andrew-gradinari force-pushed the fix-german-invalid-dates branch from aa07831 to c026dc8 Compare April 14, 2023 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants