You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Unicode Standard version 13.0.0will be released on March 10, 2020. As per usual, since the .NET runtime carries a copy of Unicode-derived data, we should update our data files to match version 13.0.0 when it's released.
This will affect the following APIs:
System.Globalization.StringInfo
System.Globalization.CharUnicodeInfo
System.Text.Encodings.Web.*
System.Text.Json.* (since it depends on System.Text.Encodings.Web)
For instructions on how to update the runtime-carried Unicode data files, consult the GenUnicodeInfo docs and the STEW docs. Also update the UnicodeUcdVersion data throughout our .csproj files (see samples).
From a cursory reading of the changes to Unicode 13.0.0 I don't believe this will result in any of our tools introducing new API surface to the System.Text.Unicode.UnicodeRanges static type.
For reference, as of this writing our derived data is based on Unicode 12.1.0.
Edit: UAX#29 was also updated as part of the Unicode 13.0.0 wave. However, the changes that are relevant to us are wholly encapsulated within the data files. The core grapheme cluster break algorithm (Sec. 3.1.1) was not changed. So we don't need to make any code changes to TextSegmentationUtility.
The text was updated successfully, but these errors were encountered:
The Unicode Standard version 13.0.0 will be released on March 10, 2020. As per usual, since the .NET runtime carries a copy of Unicode-derived data, we should update our data files to match version 13.0.0 when it's released.
This will affect the following APIs:
System.Globalization.StringInfo
System.Globalization.CharUnicodeInfo
System.Text.Encodings.Web.*
System.Text.Json.*
(since it depends onSystem.Text.Encodings.Web
)For instructions on how to update the runtime-carried Unicode data files, consult the GenUnicodeInfo docs and the STEW docs. Also update the UnicodeUcdVersion data throughout our .csproj files (see samples).
From a cursory reading of the changes to Unicode 13.0.0 I don't believe this will result in any of our tools introducing new API surface to the
System.Text.Unicode.UnicodeRanges
static type.For reference, as of this writing our derived data is based on Unicode 12.1.0.
Edit: UAX#29 was also updated as part of the Unicode 13.0.0 wave. However, the changes that are relevant to us are wholly encapsulated within the data files. The core grapheme cluster break algorithm (Sec. 3.1.1) was not changed. So we don't need to make any code changes to
TextSegmentationUtility
.The text was updated successfully, but these errors were encountered: