Skip to content
Microsoft.Recognizers.Text provides recognition and resolution of numbers, units, and date/time expressed in multiple languages (CN, EN, FR, ES, PT, DE. Partial support for NL, JA, KO). Contributions are greatly welcome! Packages are available at and
Branch: master
Clone or download
justinwilaby and tellarin Fixes validation error in several yaml files (#1500)
* Fixes validation error in several YAML files

* Correcting YAML definition merge & regen resources.
Latest commit bf2e3c6 Mar 21, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.NET Fixes validation error in several yaml files (#1500) Mar 21, 2019
.github/ISSUE_TEMPLATE Update issue templates Aug 24, 2018
Java Revise French DateTimeExtractor (#1495) Mar 19, 2019
JavaScript Fixing JavaScript security issues flagged by GitHub (#1502) Mar 21, 2019
Patterns Fixes validation error in several yaml files (#1500) Mar 21, 2019
Python Revise French DateTimeExtractor (#1495) Mar 19, 2019
Script Add script to report commit build status (#20) Jun 17, 2017
Specs Revise French DateTimeExtractor (#1495) Mar 19, 2019
.gitignore Updated a punctuation (#915) Oct 17, 2018
LICENSE Initial commit Apr 17, 2017
appveyor.yml [CI] Split build and tests script in AppVeyor (#1372) Jan 23, 2019

Microsoft Recognizers Text Overview

Build Status Build Status

Microsoft.Recognizers.Text provides robust recognition and resolution of entities like numbers, units, and date/time; expressed in multiple languages. Full support for Chinese, English, French, Spanish, Portuguese, and German. Partial support for Dutch, Japanese, and Korean. More on the way.

Utilizing the Project

Microsoft.Recognizers.Text powers pre-built entities in both LUIS: Language Understanding Intelligent Service and Microsoft Bot Framework; base entity types in Text Analytics Cognitive Service; and it is also available as standalone packages (for the base classes and the different entity recognizers).

The Microsoft.Recognizers.Text packages currently target four platforms:

Contributions are greatly welcome! Both for fixes and extensions in the currently supported languages and for expansion to new ones. Especially for Dutch, Italian, Japanese, Korean, and Turkish. More info below.


If you have any questions, please go ahead and open an issue, even if it's not an actual bug. Issues are an acceptable discussion forum as well.


This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

Good starting points for contribution are:

  • the list of open issues (especially those marked as help wanted);
  • the json spec cases temporarily marked as NotSupported (Specs); and
  • translating json test spec cases that work in English, but don't yet exist in a target language.

The links below describe the project structure and provide both an overview and tips on how to contribute (altough some steps may have become a little out-of-date). Thank you!

Supported Entities across Cultures

The table below summarizes the currently supported entities. Support for English is usually more complete than others. The primary platform is .NET (shown in table) and support should propagate to the others.

Number (cardinal) SO
Ordinal SO SO
Percentage SO SO
Unit - Age SO SO
Unit - Currency SO
Unit - Dimensions SO
Unit - Temperature SO
Choice - Boolean SO
Seq. - E-mail G G* G G G G G G G G
Seq. - GUID G G G G G G G G G G
Seq. - Social G G G G G G G G G G
Seq. - IP Address G G G G G G G G G G
Seq. - Phone Number G G G G G G G G G G
Seq. - URL G G* G G G G G G G G
DateTime (+subtypes) SP SO SI min SI min
  • G: Generic entity, not language-specific (* unicode TLDs not-supported);
  • SO: Specs-only;
  • SP: Partial specs;
  • SI: Very initial specs.
You can’t perform that action at this time.