Fix export of supplementary plane characters in font name to TTF#5396
Merged
skef merged 8 commits intofontforge:masterfrom Apr 20, 2024
Merged
Fix export of supplementary plane characters in font name to TTF#5396skef merged 8 commits intofontforge:masterfrom
skef merged 8 commits intofontforge:masterfrom
Conversation
Contributor
Author
|
Bulk tests passed with the following environment" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of change
TTF names must be encoded as UTF-16BE to support supplementary plane characters (emojis etc.). This PR fixes export and import of TTF names. The resulting font names are correctly displayed in Linux and in Windows.