Replies: 1 comment
-
I think I sorted this out in another way. In pypdf's method that deletes widgets, it is setting them also to NullObjects, which is why I think this particular error occurs. I tweaked the method in pypdf to sip over the NullObject part, and now pyHanko is giving me the same results as in my other discussion. Going to close this one in favor of the other. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is somewhat related to my other discussion, but different enough I think it warrants a new post.
I'm trying to remove some placeholders in my PDF, store their rect, and then re-add those as signatures using pyHanko. My other discussion is more about trying to sort out why pyHanko is detecting field widgets that other toolkits have deleted, while this discussion is more about wondering what I am doing wrong with pyHanko when adding these (or perhaps there is something wrong with the PDF file?)
I'm putting together another test where I remove all the widgets using pypdf instead of PyMuPDF, but I get a different error now:
Here is the sample file after having all the widgets removed using pypdf: test.pdf
This is the snippet:
I guess I'm curious if there's some other way I should be adding signatures in pyHanko. I've tried strict and non-strict mode, but there is no difference that I can see for this scenario.
Beta Was this translation helpful? Give feedback.
All reactions