Replies: 1 comment 4 replies
-
So after digging a little bit I found that PyPDF2 doesn't use fully qualified named for hierarchical form fields. That is in my case, there is "1.1.some_field" but PyPDF2 would return "some_field" only. I've implemented the fully qualified name support with optional method arguments so original behaviour is preserved. I could make a pull request if there is some interest for this feature. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As first I'm not a PDF expert and don't know all the terminology.
I've a PDF with 2 columns of the fields. Those fields have the same name but are somehow differentiated by the "set". That is, I've a sample FDF for the PDF in which when I want to fill values for the 1. column I need to use something like
<< /T (1)/Kids [ ... ]
On the other hand if I want to fill the 2. column I need to use something like
<< /T (2)/Kids [ ... ]
Now, when usin PyPDF2
update_page_form_field_values()
both column's fields ende having same values. Could I somehow set which part of the form values I want to update (even hacks for now)?I could post the .pdf if needed.
Beta Was this translation helpful? Give feedback.
All reactions