Skip to content

Conversation

@RickyDaMa
Copy link
Contributor

https://learn.microsoft.com/en-us/typography/opentype/spec/os2#ulunicoderange

Description

Not sure if this is a typo error, or research thing. I did see some sources online claiming this block starts at 0xFF000, but the Microsoft spec definitely says 0xF0000

Not sure what other checks/utils use this data, but I've written the changelog entry for the one I know about

Checklist

  • update CHANGELOG.md
  • wait for the tests to pass
  • request a review

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