Recognizers-Text
Recognizers-Text copied to clipboard
Microsoft.Recognizers.Text provides recognition and resolution of numbers, units, date/time, etc. in multiple languages (ZH, EN, FR, ES, PT, DE, IT, TR, HI, NL. Partial support for JA, KO, AR, SV). Pa...
[EN TasksMode] DateTime resolution customizations for TOD and future DateTime points under TasksMode
When Datetime Options is set as Tasksmode. 1. Next week, next month, next year will get treated as date. 2. Merge next week, next month, next year with time and...
This is just a small update to match the .NET implementation and fix the detection of "Monday 21st" / "Monday 21" / etc.
**Describe the bug** Resolution value is null in return value of ` Microsoft.Recognizers.Text.Number.NumberRecognizer.RecognizePercentage("percentage higher than 32.5%", "en-us")` **Expected behavior** 1. The resolution value should be 0.325 or "32.5%" **Sample input/output**...
**Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Use the datetime recognizer 2. Type : - "Do...
**Describe the bug** forwarded from [BotBuilder python SDK](https://github.com/microsoft/botbuilder-python/issues/1952) , giving time input between 00:00 to 00:59 to recognize_datetime() method gives invalid response that leads to DateTimePrompt giving TypeError: 'NoneType' object...
When a user provides dates in the dd mm - dd mm format, the dates are not being parsed property. Example: "21 feb - 25 feb" is interpreted as both...
**Describe the bug** If you put in the input of Recognizer.recognizeNumber function the string 'a last' you get recognizer result with the value INFINITY **To Reproduce** Steps to reproduce the...
Documentation issue only I think: it appears that "not resolved" can be returned as a value in many cases, particularly for dates (see https://github.com/microsoft/Recognizers-Text/search?p=2&q=not+resolved). Normally, the value is expected to...
Following up on PR #2894 , this implements the missing features of TimexProperty.ToString(), adding support for date ranges, date + duration, etc. This also fixes a bunch of off-by-one bugs...