DataStandardizer.Language
2.0.0
Prefix Reserved
dotnet add package DataStandardizer.Language --version 2.0.0
NuGet\Install-Package DataStandardizer.Language -Version 2.0.0
<PackageReference Include="DataStandardizer.Language" Version="2.0.0" />
<PackageVersion Include="DataStandardizer.Language" Version="2.0.0" />
<PackageReference Include="DataStandardizer.Language" />
paket add DataStandardizer.Language --version 2.0.0
#r "nuget: DataStandardizer.Language, 2.0.0"
#:package DataStandardizer.Language@2.0.0
#addin nuget:?package=DataStandardizer.Language&version=2.0.0
#tool nuget:?package=DataStandardizer.Language&version=2.0.0
Introduction
Data Standardizer provides implementations of various internationally recognised standards in data processing, covering topics ranging from languages to currencies and geographical entities. With strongly-typed enumerations for each standard (where applicable) or other targeted data types, you can represent these elements in your code such that errors with invalid values are minimised.
Supported target platforms include (modern) .Net and .Net Standard. Data Standardizer can be used in modern application software, but is also available as an option for older codebases that are being upgraded more gradually or may remain on older frameworks indefinitely.
📚 Documentation
Full documentation — user guides, concepts, and API reference for every package — is published at matthew25187.github.io/DataStandardizer.
Supporting the project
If you derive a commercial benefit from use of Data Standardizer or feel it otherwise adds value to your project, you are asked to please consider supporting the project. You can do this by becoming a GitHub sponsor to make a financial contribution. Data Standardizer is maintained and enhanced by @matthew25187 in his personal time and made available for free for all to use.
Getting Started
Installation
Data Standardizer is available as a series of packages from NuGet.org that can be linked to your existing projects. Available packages include:
| Package | Description |
|---|---|
| DataStandardizer.Chronology | Supports the following standards:<ul><li>TZ Database</li><li>Unix time</li><li>DOS date & time</li></ul> |
| DataStandardizer.Communication | Supports the following standards:<ul><li>Recommendation ITU-T E.164, The international public telecommunication numbering plan</li><li>MIME, as defined by:<ul><li>RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</li><li>RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</li><li>RFC 2047, MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</li><li>RFC 2231, MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</li><li>RFC 2397, The "data" URL scheme</li><li>RFC 2978, IANA Charset Registration Procedures</li><li>RFC 4289, Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</li><li>RFC 4648, The Base16, Base32, and Base64 Data Encodings</li><li>RFC 6657, Update to MIME regarding "charset" Parameter Handling in Textual Media Types</li><li>RFC 6838, Media Type Specifications and Registration Procedures</li><li>RFC 6839, Additional Media Type Structured Syntax Suffixes</li></ul></li></ul> |
| DataStandardizer.Core | Common types used to implement standards in the other packages. You should not need to link to this package directly. |
| DataStandardizer.File.CSV | Supports the following standards:<ul><li>RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV) Files</li></ul> |
| DataStandardizer.File.iCal | Supports the following standards:<ul><li>RFC 5545, Internet Calendaring and Scheduling Core Object Specification (iCalendar)</li><li>RFC 6868, Parameter Value Encoding in iCalendar and vCard</li><li>RFC 7986, New Properties for iCalendar</li><li>RFC 7265, jCal: The JSON Format for iCalendar</li><li>RFC 6321, xCal: The XML Format for iCalendar</li></ul> |
| DataStandardizer.File.InternetMessage | Supports the following standards:<ul><li>RFC 5322, Internet Message Format</li><li>RFC 6532, Internationalized Email Headers</li><li>RFC 6854, Update to Internet Message Format to Allow Group Syntax in the "From:" and "Sender:" Header Fields</li><li>MIME in a message, as defined by:<ul><li>RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</li><li>RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</li><li>RFC 2047, MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</li><li>RFC 2183, Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</li><li>RFC 2231, MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</li><li>RFC 2387, The MIME Multipart/Related Content-type</li><li>RFC 2392, Content-ID and Message-ID Uniform Resource Locators</li><li>RFC 3282, Content Language Headers</li></ul></li><li>RFC 2557, MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</li><li>RFC 4155, The application/mbox Media Type</li><li>Apple Mail EMLX files, which have no published standard</li></ul> |
| DataStandardizer.File.vCard | Supports the following standards:<ul><li>RFC 6350, vCard Format Specification</li><li>RFC 6868, Parameter Value Encoding in iCalendar and vCard</li><li>RFC 7095, jCard: The JSON Format for vCard</li><li>RFC 6351, xCard: vCard XML Representation</li><li>vCard 2.1, The Electronic Business Card</li><li>RFC 2425, A MIME Content-Type for Directory Information, and RFC 2426, vCard MIME Directory Profile (vCard 3.0)</li><li>RFC 2739, Calendar Attributes for vCard and LDAP</li><li>RFC 4770, vCard Extensions for Instant Messaging (IM)</li><li>RFC 9554, vCard Format Extensions for JSContact</li><li>RFC 6473, vCard KIND:application, and RFC 6869, vCard KIND:device</li><li>RFC 6474, vCard Format Extensions: Place of Birth, Place and Date of Death</li><li>RFC 6715, vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group</li><li>RFC 8605, vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP)</li></ul> |
| DataStandardizer.Geography | Supports the following standards:<ul><li>ISO 3166-1, Codes for the representation of names of countries and their subdivisions – Part 1: Country code</li><li>ISO 3166-2, Codes for the representation of names of countries and their subdivisions – Part 2: Country subdivision code</li><li>UN M49, Standard Country or Area Codes for Statistical Use (Series M, No. 49)</li></ul> |
| DataStandardizer.Language | Supports the following standards:<ul><li>ISO 639, Code for the representation of names of languages</li><ul><li>Part 1: Alpha-2 code</li><li>Part 2: Alpha-3 code</li><li>Part 3: Alpha-3 code for comprehensive coverage of languages</li><li>Part 5: Alpha-3 code for language families and groups</li></ul><li>ISO 15924, Codes for the representation of names of scripts</li></ul> |
| DataStandardizer.LanguageTag | Supports the following standards:<ul><li>IETF BCP 47 language tags, as defined by:<ul><li>RFC 5646, Tags for Identifying Languages, including well-formed and valid tags, and the IANA Language Subtag Registry format</li></ul></li></ul> |
| DataStandardizer.Money | Supports the following standards:<ul><li>ISO 4217, Codes for the representation of currencies and funds</li><ul><li>Table A.1 – Current currency & funds code list</li><li>Table A.2 – Current funds codes</li><li>Table A.3 – List of codes for historic denominations of currencies & funds</li></ul><li>Money type, as described in Patterns of Enterprise Application Architecture by Martin Fowler</li></ul> |
To use a particular standard in your application, find the corresponding package from the above list and add it as a dependency to your project. Instructions for doing so will depend on what development tooling you are using.
- Visual Studio: see Install and manage packages in Visual Studio using the NuGet Package Manager
- .Net CLI: see Install and manage NuGet packages with the dotnet CLI
- Visual Studio Code: see NuGet in Visual Studio Code
See the Get started guide for step-by-step installation and a quickstart.
Software dependencies
Depending on which .Net platform you are targeting, the above packages will also depend on various other system- and third-party packages. They will be included as static dependencies where required and should be automatically resolved, but if you are using a proxy for your package server you may need to make sure these other packages are also available. For example, the netstandard1.1 and netstandard2.0 builds of DataStandardizer.LanguageTag depend on System.Memory for their span-based API.
Latest releases
The promoted version is the latest release promoted from this repository's builds (a GitHub Release). It does not necessarily correspond with the latest package version published to NuGet or any other publically available source.
Build and test
Data Standardizer is open source so you can read, build, and adapt it for your own use. The project does not currently accept third-party code contributions; the instructions below are provided as a convenience for working with your own copy or fork of the repository.
After cloning the repository, you can compile the entire solution from the repository root:
dotnet build DataStandardizer.sln
and run the XUnit-based tests with:
dotnet test DataStandardizer.sln
Per-package solution filter (*.slnf) files let you build or test a single package in isolation. For the full branching strategy, per-package builds, IDE testing, and the PowerShell scripts that regenerate the standard enums, see Build from source in the documentation.
Usage
Though each package contains many types, typically there are only a few you will use directly in your application. See the project documentation for user guides, concepts, and API reference covering each package — including built-in CSV reading, writing, and normalization in DataStandardizer.File.CSV, iCalendar reading, writing, and recurrence expansion in DataStandardizer.File.iCal, reading and writing of Internet messages in EML, MHTML, mbox and EMLX files in DataStandardizer.File.InternetMessage, and reading, writing and conversion of vCard 4.0, 3.0 and 2.1 cards, jCard and xCard in DataStandardizer.File.vCard.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp1.0 was computed. netcoreapp1.1 was computed. netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard1.0 is compatible. netstandard1.1 was computed. netstandard1.2 was computed. netstandard1.3 was computed. netstandard1.4 was computed. netstandard1.5 was computed. netstandard1.6 was computed. netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen30 was computed. tizen40 was computed. tizen60 was computed. |
| Universal Windows Platform | uap was computed. uap10.0 was computed. |
| Windows Phone | wp8 was computed. wp81 was computed. wpa81 was computed. |
| Windows Store | netcore was computed. netcore45 was computed. netcore451 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 1.0
- DataStandardizer.Core (>= 2.0.0)
- NETStandard.Library (>= 2.0.3)
- System.Text.RegularExpressions (>= 4.3.1)
-
.NETStandard 2.0
- DataStandardizer.Core (>= 2.0.0)
-
net10.0
- DataStandardizer.Core (>= 2.0.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on DataStandardizer.Language:
| Package | Downloads |
|---|---|
|
DataStandardizer.LanguageTag
Data Standardizer provides implementations of various internationally recognised standards in data processing, covering topics ranging from languages to currencies and geographical entities. With strongly-typed enumerations for each standard (where applicable) or other targeted data types, you can represent these elements in your code such that errors with invalid values are minimised. Includes: - Supports use of IETF BCP 47 language tags as defined by RFC 5646, checking that a tag is well-formed, or valid against a copy of the IANA Language Subtag Registry. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated | |
|---|---|---|---|
| 2.0.0 | 369 | 11/10/2026 | |
| 1.2.0-preview.2 | 66 | 11/6/2026 | |
| 1.1.0 | 6,132 | 1/10/2026 | |
| 1.0.0 | 378 | 12/7/2025 | |
| 1.0.0-preview.3 | 177 | 12/6/2025 | |
| 1.0.0-preview.1 | 234 | 9/25/2025 |
Breaking changes:
- The packages no longer have a `net8.0` build. An application on .NET 8 or .NET 9 gets a .NET Standard build, without the APIs that only the `net10.0` build has, such as `DateOnly` and `TimeOnly` support. To keep those APIs, move the application to .NET 10.
- The `netstandard1.x` and `netstandard2.0` builds no longer list `JetBrains.Annotations` as a NuGet dependency. If your code uses its attributes and you got the package through DataStandardizer, add a reference to `JetBrains.Annotations` to your project.
Fixed:
- Debuggers can step into the packages' source through Source Link.
- `CompareTo` on the ISO 639 code types (`Iso639Part1Language`, `Iso639Part2BLanguage`, `Iso639Part2TLanguage`, `Iso639Part3Language` and `Iso639Part5LanguageFamily`) orders two codes instead of throwing `ArgumentException`, so lists of codes can be sorted.
- `CompareTo` on an ISO 639 code type returns 1 for `null`, as `IComparable` requires, instead of throwing `ArgumentNullException`.
- `CompareTo` on a default instance of an ISO 639 code type throws `InvalidOperationException` instead of `NullReferenceException`.
- On .NET 10, `GetDate`, `GetAge`, `GetAlias`, `GetEnglishName` and `GetFrenchName` on an `Iso15924Script` no longer return a wrong date or throw when the current culture uses a non-Gregorian calendar, such as th-TH or ar-SA.
Changed:
- The netstandard1.x and netstandard2.0 builds now carry nullable annotations, so projects on C# 8 or later with nullable enabled get null warnings from them.