<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Allow PDF form export with different defaults based on Archive setting" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126642#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Allow PDF form export with different defaults based on Archive setting" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126642">bug 126642</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>(In reply to Thorsten Behrens (CIB) from <a href="show_bug.cgi?id=126642#c4">comment #4</a>) > First, confirm - this inconsistency is there. > > Secondly, as A/2 definitely permits forms - why remove the functionality, > now that it's fixed and even validating? Why not give users the option to > export (or not)? Ok - so the updated patch will actually enable form export for any PDF, but still fix the handling of the overriding value of UseTaggedPDF, if PDF/A is selected. I've done a backport for pre-6-3, which will just disable PDF/A form export. (In reply to Heiko Tietze from <a href="show_bug.cgi?id=126642#c3">comment #3</a>) > Dislike another checkbox with almost the same name. Why not disable/uncheck > for A1 likewise its done for Tagged PDF? I don't follow you here. The disabling is done for Tagged PDF, because PDF/A requires the document to be tagged. My problem is different. Per default LO generates PDF forms, which are changeable by the user. PDF/A is used for archiving, so you almost always want to generate PDF/A without active form elements. For example a checkbox will be replaced by an image of the required state, so a user can't change it, even by accident. Still PDF/A also allows a valid PDF to contain active form elements. That's why Thorsten says the decision should be up to the user, now that PDF/A export with active forms works correct. My point is just that the very most of the users want to generate normal PDF forms but no PDF/A forms for archiving. And I thought it might be a good idea to offer two distinct "Create form" settings. Maybe in the end this is not needed, or the usability is even worse, as now the user has to remember to manually switch the "create form" setting based on the selected target PDF type.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>