PDFBOX-5808: Add support for LookupType3 Alternate Set #190
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
Refactor CompoundCharacterTokenizer to handle colliding ligatures
|
I forgot to add a close message to the commit, please close it yourself. |
|
Changes were pulled in, closing this PR |
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.
Refactor CompoundCharacterTokenizer to handle colliding ligatures
I'm not certain about the CompoundCharacterTokenizer refactor but it's purpose could be refocused on glyphs handling only, hence the proposed modification. Split by words has been moved to StringUtil
I tried to respect code formatting as much as possible