https://bugs.documentfoundation.org/show_bug.cgi?id=167291
--- Comment #7 from Dave Gilbert <[email protected]> --- Form editing in PDF has multiple meanings, and what people use LO for varies; so hmm: a) Using LO to overwrite a PDF with some other text, or a signature or something - nothing special there; we just have to gently improve the PDF loading. b) Filling in the *fields* of a basic PDF form; again not that hard in principal - if we can find fields we can probably turn them into editable things. c) PDF can have Javascript associated with field changes; for example I've seen a government form that updates a 'total' at the bottom of a numeric column. IMHO that's a massive job (and even things like Okular are bad at it). d) Saving a loaded PDF form that's had it's form filled in, such that the form data in the saved PDF is stored in a way that a tool can extract automatically as it would if the form was filled in using another PDF viewer. IMHO that's a more detailed job; and harder to do generally - people would get very surprised when they submit their government derived PDF form and find the government misreads it. (Ahem I might have already had that happen using Okular to fill in a Government form...) So what to people use LO for editing a PDF for ? IMHO (a) is what I use LO for here, not (b..d) - b..d I use my Okular or Chrome for. You could have a mode that was like the 'insert pdf' which uses poppler to do *rendering* of the form and then you create editables for all the form elements and do the stuff to do (d) - including (c) as well would be a big job. But again, IMHO I think (a) is what I want to use LO for when editing a PDF. -- You are receiving this mail because: You are the assignee for the bug.
