Canonicalize font subset tags - #38
Merged
Merged
Conversation
A subset font's name carries a six letter tag (/BaseFont /IIJUVL+OpenSans) that some producers, Aspose.PDF among them, pick at random on every save. Each distinct tag after /BaseFont or /FontName is now replaced, in order of first appearance, with AAAAAA, AAAAAB, and so on. The replacement is length-preserving, so the cross-reference table needs no repair, and an already normalized document maps each tag onto itself, so a second pass changes and reports nothing.
This was referenced Sep 30, 2026
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
1 participant
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.
A subset font's name carries a six letter tag (/BaseFont /IIJUVL+OpenSans) that some producers, Aspose.PDF among them, pick at random on every save. Each distinct tag after /BaseFont or /FontName is now replaced, in order of first appearance, with AAAAAA, AAAAAB, and so on. The replacement is length-preserving, so the cross-reference table needs no repair, and an already normalized document maps each tag onto itself, so a second pass changes and reports nothing.