-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Closed
Labels
📌 seQUESTeredIdentifies that an issue has been imported into Quest.Identifies that an issue has been imported into Quest.dotnet-fundamentals/svcin-prThis issue will be closed (fixed) by an active pull request.This issue will be closed (fixed) by an active pull request.okr-qualityContent-quality KR: Concerns article defects (bugs), freshness, or build warnings.Content-quality KR: Concerns article defects (bugs), freshness, or build warnings.
Description
Type of issue
Typo
Description
Beginning with .NET Core 3.0, the System.Text.Rune type represents a Unicode scalar value. Rune is not available in .NET Core 2.x or .NET Framework 4.x.
If you run this code in .NET Framework or .NET Core 3.1 or earlier, the text element count for the emoji shows 4. That is due to a bug in the StringInfo class that was fixed in .NET 5.
- Second quotation is flawed by fact that, AFAIK,
Runeis available only to .NET from version Core 3.0. - First quotation suggest that earlier versions of Framework have
Runewhile only 4.x versions does not. Similar applies to ..NET Core prior 2.x.
Page URL
https://learn.microsoft.com/en-us/dotnet/standard/base-types/character-encoding-introduction
Content source URL
https://github.com/dotnet/docs/blob/main/docs/standard/base-types/character-encoding-introduction.md
Document Version Independent Id
d53a0764-9f27-16b3-c40a-9627dd1bcc0d
Article author
Metadata
- ID: a6cf7421-fbd2-0ca0-7385-4df65531fd66
- Service: dotnet-fundamentals
Metadata
Metadata
Assignees
Labels
📌 seQUESTeredIdentifies that an issue has been imported into Quest.Identifies that an issue has been imported into Quest.dotnet-fundamentals/svcin-prThis issue will be closed (fixed) by an active pull request.This issue will be closed (fixed) by an active pull request.okr-qualityContent-quality KR: Concerns article defects (bugs), freshness, or build warnings.Content-quality KR: Concerns article defects (bugs), freshness, or build warnings.