Merged
Conversation
Support for the ZapfDingbats font was added. Additionally, the text example now conforms to the PDF standard.
Owner
|
Thank you again, @hummingly for your work on being able to use the dingbats properly! |
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.
The notes with (CUS -> Corporate Use Subarea) indicate symbols that cannot be displayed (radicalex in Symbol cannot probably displayed too) but that's not a problem for most users. As noted before the base encoding has to be either WinAnsiEncoding or MacRomanEncoding or MacExpertEncoding. I also have MacRomanEncoding (and StandardEncoding) in a branch already. However, that one has a lot of breaking changes.