implement support and tests for cmap format 13 #647
Merged
Conversation
This file contains 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
Connum
force-pushed
the
feature/cmap-format13
branch
from
d540816 to
1cdb83f
Compare
yne
approved these changes
Nov 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Implements support for cmap table format 13
(also stops tracking of the dist files which was accidentally reintroduced by #503)
Motivation and Context
fixes #105
The newly added test case in the unicode test suite will show the characters as not passing because of differences in the SVG paths, but it will output the correct glyphs.
How Has This Been Tested?
npm run testand running the unicode test suite locally.Screenshots (if appropriate):
Types of changes
Checklist:
npm run testand all tests passed green (including code styling checks).