Add support for NeedAppearances #70
Open
Conversation
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
Any PDF that uses NeedAppearances true relies on the reader to construct appearance streams for all widget annotations.
|
After applying this fix you may notice that the multi-line TRUSTEE name/address in the top-left corner shows up funny, with extra space between each line, but that is a separate issue, which I provided a fix for here: |
|
Why are fixes ignored? |
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.
Any PDF that uses
NeedAppearances truerelies on the reader to construct appearance streams for all widget annotations.I received a 1099-SA tax form from my HSA provider this year and noticed using SumatraPDF that several fields were missing (invisible). However, all other PDF readers are able to display all fields.
Here is the (anonymized) PDF:
f1099sa.pdf
Screenshot below illustrates the problem (with Firefox on the left and MuPDF before this fix on the right):
