You can generate the form from the attached HTML like this:
prince --pdf-forms simple-form.html
This creates a form that can be filled in with Acrobat or other PDF viewers and saved or printed. You may also wish to specify --pdf-profile=PDF/UA-1 for accessibility.
Most HTML form controls are supported and it is also possible to include submit and reset buttons, although not every PDF viewer supports these yet.
The new --pdf-forms option is a shorthand for applying "prince-pdf-form: enable" to all of the form elements; this new CSS property allows individual form elements to be selectively enabled or disabled. We may enable PDF Forms by default in Prince 15.
So, would you recommend a "latest build" in production? Not being backwards compatible means that a feature introduced in a "latest build" might break/behave differently in a future release, is that right?
We try to avoid this, but new features can shift in response to early feedback, yes. There is a bit of a chicken and egg issue if nobody uses it until it's frozen and we can't freeze it until people use it.
Hi Mike, I don't think there is a clear answer, so I'll attempt to ask this question again. When will this PDF forms feature make its way to the numbered release (official)? I have done some local testing, and it looks like the latest numbered release, 14.3, doesn't have it yet. This is very important to us.
Hi Make, I have downloaded an example from this page, simple-form.pdf, and when I opened it in the Acrobat Reader application, all the input text showed up as squares. However, it seems to work fine when the same pdf is opened in the browser (Chrome in my case). Please see the screenshots below.
I wonder what causes this and how this issue can be solved.
Hi Mike, I did some digging, and it looks like the font reference attached to the form field have the weird prefix PXAAAA+. Please see the attached screenshot for more details. I'm seeing the same thing when I generate my PDF with forms. In my case, it referencing PXAAAA+Helvetica
First off, this is an amazing add and will save us a lot of time.
Quick feature request, could it also read the html "type" attribute and create applicable PDF fields based on that? Such as input type="date" making a "Date" field in the PDF and input type="number" using number formatting by default (Bonus points for reading the min, max and pattern attributes as well for this!). Would also like to replicate the native "Digital Signature" field you can add in Acrobat if possible. Thanks!