[API Proposal]: Add UnicodeRanges.ArabicExtendedB to System.Text.Encodings.Web

[GrabYourPitchforks]

Proposal

namespace System.Text.Unicode
{
    // existing type
    public static class UnicodeRanges
    {
        // new API
        public static UnicodeRange ArabicExtendedB { get; }
    }
}

Discussion

When new versions of Unicode are released, we ingest them into .NET. Typically this ingestion is nothing more than updating the data tables backing System.Private.CoreLib and System.Text.Encodings.Web and does not require new API surface. However, on occasion Unicode will add new blocks to the BMP, and since we expose block information via the UnicodeRanges type, we need to update that type to account for these introductions. This allows consumers of System.Text.Encodings.Web to granularly allow or disallow characters from these blocks to appear unescaped on the wire.

The file which contains these APIs is located here and is generated by a tool.

As part of #44423, when Unicode 14.0 is released on September 14, we will ingest that data into .NET 7. They're adding a new block Arabic Extended-B to the BMP (more info). This API proposal is to support this new block's usage within our apps.

[ghost]

Tagging subscribers to this area: @tarekgh, @eiriktsarpalis, @layomia
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Proposal

namespace System.Text.Unicode
{
    // existing type
    public static class UnicodeRanges
    {
        // new API
        public static UnicodeRange ArabicExtendedB { get; }
    }
}

Discussion

When new versions of Unicode are released, we ingest them into .NET. Typically this ingestion is nothing more than updating the data tables backing System.Private.CoreLib and System.Text.Encodings.Web and does not require new API surface. However, on occasion Unicode will add new blocks to the BMP, and since we expose block information via the UnicodeRanges type, we need to update that type to account for these introductions. This allows consumers of System.Text.Encodings.Web to granularly allow or disallow characters from these blocks to appear unescaped on the wire.

As part of #44423, when Unicode 14.0 is released on September 14, we will ingest that data into .NET 7. They're adding a new block Arabic Extended-B to the BMP (more info). This API proposal is to support this new block's usage within our apps.

Author:	GrabYourPitchforks
Assignees:	-
Labels:	area-System.Text.Encodings.Web, api-ready-for-review
Milestone:	7.0.0

[terrajobst]

This looks very reasonable

[GrabYourPitchforks]

@terrajobst What would be really nice is if I could correct the capitalization on some existing properties without breaking consumers. ;)

[tarekgh]

What would be really nice is if I could correct the capitalization on some existing properties without breaking consumers. ;)

Expose new properties with right capitalization and hide the old ones :-)

[terrajobst]

Meh. Crypto is living proof that having the wrong capitalization isn't a world ending event :-)

[tarekgh]

Meh. Crypto is living proof that having the wrong capitalization isn't a world ending event :-)

I was kidding :-)
One option we can file issue for C# compiler to be not case sensitive and just break the world :-) ... kidding again.

[terrajobst]

There is virtualized casing mode for the C# compiler, called vbc 😝

[terrajobst]

Video

Looks good as proposed

namespace System.Text.Unicode
{
    // existing type
    public static class UnicodeRanges
    {
        // new API
        public static UnicodeRange ArabicExtendedB { get; }
    }
}

[bgrainger]

The file which contains these APIs is located here and is generated by a tool.

I opened a PR with the updates from running the tool: #63901