Skip to content

Conversation

@jmcwilliams403
Copy link

Microsoft is clearly disinterested in keeping Windows' internal Unicode information up to date.
According to this documentation article on their website, newer versions of the dotnet standard don't even use it anymore, opting instead to pull straight from the ICU. This is a workaround.
Unicode character properties are a whole other issue, but this patch's inclusion of unicodetools makes it possible.

Proof that this patch does indeed work:

screenshot of sequences window showing Latin Extended-F superscript sequences

Microsoft is clearly disinterested in keeping Windows' internal Unicode information up to date. According to https://learn.microsoft.com/en-us/dotnet/core/extensions/globalization-icu newer versions of the dotnet standard don't even use it anymore, opting instead to pull straight from the ICU. This is a workaround.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant