test-mass-forker-org-1 / recognizers-text

Microsoft.Recognizers.Text provides recognition and resolution of numbers, units, and date/time expressed in multiple languages (ZH, EN, FR, ES, PT, DE, IT, TR, HI, NL. Partial support for JA, KO, AR, SV). Contributions are greatly welcome! Packages are available at https://www.nuget.org/profiles/Recognizers.Text and https://www.npmjs.com/~recognizers.text

Microsoft Recognizers Text Overview

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, German, Italian, Turkish, Hindi, and Dutch. Partial support for Japanese, Korean, Arabic, and Swedish. More on the way.

Utilizing the Project

Microsoft.Recognizers.Text powers pre-built entities in LUIS: Language Understanding Intelligent Service, Power Virtual Agents, 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:

• C#/.NET - NuGet packages available at: https://www.nuget.org/profiles/Recognizers.Text
• JavaScript/TypeScript - NPM packages available at: https://www.npmjs.com/~recognizers.text
• Python - PyPI packages available at: https://pypi.org/user/recognizers-text/ (alpha)
• Java (in progress)

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

.NET is the primary package version and contributions propagate to the other platforms with time.

Help

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.

Contributing

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] 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 (although some steps may have become a little out-of-date). Thank you!

• Overview and language resources
• Implementing language specific behaviour
• Test specs and testing in general

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.

Entity Type	EN	ZH-CN	NL	FR	DE	IT	JA	KO	PT	ES
Number (cardinal)	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓
Ordinal	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓
Percentage	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓
Number Range	✓	✓	✓	✓	✓	✓	PA/EO	✓	❌	✓
Unit - Age	✓	✓	✓	✓	✓	✓	✓	PA/EO	✓	✓
Unit - Currency	✓	✓	✓	✓	✓	✓	✓	PA/EO	✓	✓
Unit - Dimensions	✓	✓	✓	✓	✓	✓	✓	PA/EO	✓	✓
Unit - Temperature	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓
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)	✓	✓	✓	✓	✓	✓	SO	SO	✓	✓

Entity Type	SV	BG	TR	HI	AR
Number (cardinal)	✓	❌	✓	✓	PA/EO
Ordinal	✓	❌	✓	✓	PA/EO
Percentage	✓	❌	✓	✓	PA/EO
Number Range	❌	❌	✓	✓	PA/EO
Unit - Age	✓	❌	✓	✓	❌
Unit - Currency	✓	❌	✓	✓	❌
Unit - Dimensions	✓	❌	✓	✓	❌
Unit - Temperature	✓	❌	✓	✓	❌
Choice - Boolean	✓	✓	✓	✓	✓
Seq. - E-mail	G	G	G	G	G
Seq. - GUID	G	G	G	G	G
Seq. - Social	G	G	G	G	G
Seq. - IP Address	G	G	G	G	G
Seq. - Phone Number	❌	❌	❌	❌	❌
Seq. - URL	G	G	G	G*	G*
DateTime (+subtypes)	❌	❌	✓	✓	SO

• G: Generic entity, not language-specific (* unicode TLDs not-supported);
• EO: Extraction-only (parsing/resolution/normalization pending);
• PA: Partial support (type not fully supported);
• SO: Specs-only (test specs coverage OK, but support pending);
• SP: Partial specs;
• SI: Very initial specs (typically language support start for a new language).