DataStandardizer.Communication 2.0.0

Prefix Reserved
dotnet add package DataStandardizer.Communication --version 2.0.0
                    
NuGet\Install-Package DataStandardizer.Communication -Version 2.0.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="DataStandardizer.Communication" Version="2.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="DataStandardizer.Communication" Version="2.0.0" />
                    
Directory.Packages.props
<PackageReference Include="DataStandardizer.Communication" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add DataStandardizer.Communication --version 2.0.0
                    
#r "nuget: DataStandardizer.Communication, 2.0.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package DataStandardizer.Communication@2.0.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=DataStandardizer.Communication&version=2.0.0
                    
Install as a Cake Addin
#tool nuget:?package=DataStandardizer.Communication&version=2.0.0
                    
Install as a Cake Tool

Introduction

OpenSSF Scorecard

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.

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

Package Promoted version nuget.org Release build
DataStandardizer.Chronology DataStandardizer.Chronology promoted version DataStandardizer.Chronology on nuget.org Release build
DataStandardizer.Communication DataStandardizer.Communication promoted version DataStandardizer.Communication on nuget.org Release build
DataStandardizer.Core DataStandardizer.Core promoted version DataStandardizer.Core on nuget.org Release build
DataStandardizer.File.CSV DataStandardizer.File.CSV promoted version DataStandardizer.File.CSV on nuget.org Release build
DataStandardizer.File.iCal DataStandardizer.File.iCal promoted version DataStandardizer.File.iCal on nuget.org Release build
DataStandardizer.File.InternetMessage DataStandardizer.File.InternetMessage promoted version DataStandardizer.File.InternetMessage on nuget.org Release build
DataStandardizer.File.vCard DataStandardizer.File.vCard promoted version DataStandardizer.File.vCard on nuget.org Release build
DataStandardizer.Geography DataStandardizer.Geography promoted version DataStandardizer.Geography on nuget.org Release build
DataStandardizer.Language DataStandardizer.Language promoted version DataStandardizer.Language on nuget.org Release build
DataStandardizer.LanguageTag DataStandardizer.LanguageTag promoted version DataStandardizer.LanguageTag on nuget.org Release build
DataStandardizer.Money DataStandardizer.Money promoted version DataStandardizer.Money on nuget.org Release build

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 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.1 is compatible.  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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (3)

Showing the top 3 NuGet packages that depend on DataStandardizer.Communication:

Package Downloads
DataStandardizer.File.iCal

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. Provides types supporting the reading and writing of iCalendar files. Includes: - Internet Calendaring and Scheduling Core Object Specification (iCalendar), RFC 5545 - Parameter Value Encoding in iCalendar and vCard, RFC 6868 - New Properties for iCalendar, RFC 7986 - jCal: The JSON Format for iCalendar, RFC 7265 - xCal: The XML Format for iCalendar, RFC 6321

DataStandardizer.File.InternetMessage

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. Provides types supporting the reading and writing of Internet messages, including: - RFC 5322 and RFC 6532: a streaming reader of the header fields of a message, with UTF-8 in field bodies - RFC 2045 and RFC 2046: a streaming reader of the MIME entities of a message, with multipart bodies, embedded messages and transfer decoding - RFC 5322, RFC 6532, RFC 2045 and RFC 2046: streaming writers of header fields and MIME entities, with folding, transfer encoding, multipart boundaries and byte-exact copying of what has not changed - RFC 5322, RFC 6532 and RFC 6854: typed addresses, mailboxes, groups, message identifiers and keyword phrases, parsed from the modern and obsolete syntax and written in the modern form where the modern syntax can express them - RFC 5322: typed date-times, parsed from the modern and obsolete syntax and written in the modern form, which keep an unknown UTC offset (-0000), a leap second and whether a day of the week was given - RFC 2047: encoded words in display names, keyword phrases, comments and unstructured fields, decoded when read and written where text is not US-ASCII - RFC 2045, RFC 2183, RFC 2231, RFC 2392 and RFC 3282: the MIME-Version, Content-Type, Content-Transfer-Encoding, Content-ID, Content-Description, Content-Disposition and Content-Language header fields, with cid: URIs - RFC 5322 and RFC 6854: a message object model with typed accessors for the origination, destination, identification, informational, resent and trace fields, a reader and writer that keep unchanged fields byte for byte, and the conformance checks of RFC 5322 §3.6 - RFC 2045, RFC 2046, RFC 2387 and RFC 2392: a MIME entity tree with decoded content, text and HTML bodies, attachments, cid: lookup, a message builder, and a writer that rewrites only what has changed - RFC 2557 and RFC 2387: MHTML files, with Content-Location, the root of a multipart/related entity, URLs resolved to their parts, a document builder, and a reader and writer - RFC 4155: mbox files in the mboxrd, mboxo, mboxcl and mboxcl2 variants, with a reader that takes one message at a time, so a mailbox of any size can be processed, and a writer - Apple Mail EMLX files: a message with its byte count and its property list of metadata, with typed flags and dates, unknown keys kept, partial files with their parts supplied by the caller, and a reader and writer

DataStandardizer.File.vCard

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. Provides types supporting the reading and writing of vCard files. Includes: - vCard Format Specification, RFC 6350 (content lines, value types, the card object model, and reading and writing cards with conformance checks) - Parameter Value Encoding in iCalendar and vCard, RFC 6868 - jCard: The JSON Format for vCard, RFC 7095 (reading and writing cards as JSON, on .NET Standard 2.0 and later) - xCard: vCard XML Representation, RFC 6351 (reading and writing cards as XML) - vCard 2.1 (reading and writing vCard 2.1 cards, with quoted-printable, BASE64, CHARSET, parameters with no name and the card an AGENT holds) - vCard MIME Directory Profile, RFC 2426, and MIME Content-Type for Directory Information, RFC 2425 (reading and writing vCard 3.0 cards, and converting between versions) - Calendar Attributes for vCard and LDAP, RFC 2739 - vCard Extensions for Instant Messaging, RFC 4770 - vCard Format Extensions for JSContact, RFC 9554 - vCard KIND:application, RFC 6473, and vCard KIND:device, RFC 6869 - vCard Format Extensions: Place of Birth, Place and Date of Death, RFC 6474 - vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group, RFC 6715 - vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol, RFC 8605

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.0 217 11/10/2026
1.1.1 1,227 10/8/2026
1.1.0 747 1/10/2026
1.0.0-preview.1 243 12/15/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.

New:
- `MimeMediaType` parses, formats and compares media types such as `text/plain;charset=us-ascii` (RFC 2045 §5.1), with `Suffix` (RFC 6839) and `Tree` (RFC 6838).
- `MimeParameter` holds a media type parameter's name and decoded value.
- `MimeTopLevelTypes` and `MimeMediaType` constants for the registered top-level types and common media types.
- `MimeTransferEncoding` represents a Content-Transfer-Encoding mechanism, such as `base64` or an `x-` extension, with `IsIdentity` and `Domain` (`MimeDataDomain`) to tell what data a transport must carry.
- `MimeBase64Encoder` and `MimeBase64Decoder` encode and decode base64 buffer by buffer, as the RFC 2045 `base64` Content-Transfer-Encoding (`MimeBase64Mode.Mime`) or the strict RFC 4648 form of iCalendar BINARY values and RFC 2047 "B" encoded words (`MimeBase64Mode.Strict`); `MimeBase64` has one-shot and length methods.
- `MimeQuotedPrintableEncoder` and `MimeQuotedPrintableDecoder` encode and decode quoted-printable buffer by buffer, as the RFC 2045 `quoted-printable` Content-Transfer-Encoding (`MimeQuotedPrintableMode.Body`) or the RFC 2047 "Q" encoding of encoded words in text, comment or phrase context; `MimeQuotedPrintable` has one-shot and length methods and `EndsWithSoftLineBreak`.
- Add MimeCharset and MimeCharsetResolver for character set names and their encodings.
- Add MimeDataUri for RFC 2397 data: URIs.
- `MimeMediaType` decodes RFC 2231 parameter sections and extended values (character set and language), and rejects anything RFC 2231 doesn't allow unless the caller opts in with a `MimeMediaTypeParseOptions` member: `AllowMissingSections`, `AllowDuplicateSections` and `AllowLeadingZeroSectionNumbers` (together, `AllowNonstandardSections`), `AllowQuotedExtendedValues` and `AllowLowercaseHexDigits` (together, `AllowNonstandardExtendedValues`), `AllowUnknownCharsets` and `AllowInvalidOctets`.
- `MimeParameter` takes values that aren't US-ASCII and an optional RFC 1766 language, writes them as RFC 2231 extended values, and splits long parameters into sections with `FormatSections`.
- `MimeEncodedWord` reads and writes RFC 2047 encoded words in header text, with RFC 2231 languages; `EncodeText` writes text as encoded words and `DecodeText` decodes a run of text, with `MimeEncodedWordParseOptions` opt-ins for words that don't follow the rules.
- `ItuE164InternationalNumber` has `==` and `!=` operators.

Fixed:
- TelephonyInfo.CurrentTelephony no longer throws when the current culture is the invariant culture.
- On netstandard1.1, RFC 2231 parameter values whose octets aren't valid in their character set are no longer accepted unless `AllowInvalidOctets` is given.
- The `netstandard1.1` build depends on `System.Net.Http` 4.3.4 instead of 4.3.2, which has a known vulnerability.
- Debuggers can step into the packages' source through Source Link.
- Accept raw UTF-8 in a quoted Content-Type parameter value (RFC 6532 §3.2).
- `ItuE164InternationalNumber` values that are equal have the same hash code, and `Equals(object)` agrees with `Equals(ItuE164InternationalNumber)`, so hash-based collections find equal numbers.
- TelephonyInfo country constructors load the number format for that country, not the invariant one.
- ItuE164InternationalNumber.Parse and TryParse reject more than 15 digits when the international prefix symbol is not allowed.
- `ItuE164InternationalNumber.Parse` and `TryParse` reject leading white space unless `AllowLeadingWhite` is set, and a final line feed unless `AllowTrailingWhite` is set.
- `ItuE164InternationalNumber.Parse` and `TryParse` no longer treat control characters other than U+0009 to U+000D as white space or as separators.
- A utf-16 or utf-32 decoder from MimeCharsetResolver looks for a byte order mark again after a flush.
- `ItuE164InternationalNumber.ToString(format, provider)` and `ToString(provider)` format the number, not the type name, when the provider is `null` or a `CultureInfo`, so `string.Format` with a culture formats it too.
- TelephonyInfo.CurrentTelephony gives the default instance for a culture whose region is a UN M.49 code.
- The network `IdentificationCode` and `SubscriberNumber` of an `ItuE164InternationalNumber` throw `InvalidOperationException`, not `ArgumentOutOfRangeException`, when the number ends inside its identification code.
- The invariant `i` and `I` formats of `ItuE164InternationalNumber` write the international prefix symbol `+` and the whole Country Code, such as `+44 3071234567`, instead of a literal `p` and only the first digit of the Country Code.
- `ItuE164InternationalNumber.ToString` formats a `null`, empty or white-space format as the default `G` format, instead of returning an empty string, so `string.Format("{0}", number)` and `$"{number}"` print the number.
- The ulong E.164 factories reject a number without an assigned Country Code or Identification Code.
- The typed E.164 factories reject a National Significant Number or Subscriber Number with no digits.

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.
- MimeBase64Encoder encodes MIME lines about ten times faster on .NET 10.
- MimeBase64.TryDecode and Decode allocate one array for padded data.
- `ItuE164InternationalNumber.ToString` returns an empty string, not the type name, when a format provider's own formatter returns `null`.
- `ItuE164InternationalNumber.ToString` reads a format longer than one character as a custom pattern, even when it begins with `g`, `G`, `i` or `I`.