You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just finished a form with l3pdffield-testphase. If one wants to protect further editing, one can either protect the editing functions with a password (which the FF pdfviewer gladly ignores (see mozilla/pdf.js#14356)) or print the form to a new PDF file. Unfortunately the pdffields created by l3pdffield-testphase are set to be visible, but unprintable by default.
When one creates a form in Adobe Acrobat, the form elements are visible and printable by default. IMHO l3pdffields should do the same and add print as a default annotation flag.
The text was updated successfully, but these errors were encountered:
the Print flag is not set by default. You can set it for a field or for a type of fields e.g. with \pdffield_setup:n{preset-textfield={setF=Print}}. If you use a A-standard, e.g. with pdfstandard=a-2b in \DocumentMetadata the print flag will be forced too.
That's what I did of course. This issue was only ment as a feedback. The \ChoiceMenu from hyperref has the print flag set by default, Acrobat sets it be default when creating a form so I just think l3pdffields should set it as well.
I just finished a form with l3pdffield-testphase. If one wants to protect further editing, one can either protect the editing functions with a password (which the FF pdfviewer gladly ignores (see mozilla/pdf.js#14356)) or print the form to a new PDF file. Unfortunately the pdffields created by l3pdffield-testphase are set to be visible, but unprintable by default.
When one creates a form in Adobe Acrobat, the form elements are visible and printable by default. IMHO l3pdffields should do the same and add
print
as a default annotation flag.The text was updated successfully, but these errors were encountered: