3 ms·
I don't know about you, but >98% of the PDFs I use are just for reading and don't contain a fillable form. And implementing a PDF viewer is already a major und
by gpvos 6y ago
I don't know about you, but >98% of the PDFs I use are just for reading and don't contain a fillable form.
And implementing a PDF viewer is already a major undertaking; adding the form functionality complicates things even more.
- nip 6y agoI posted a link (above) to the app I built to solve that problem. The vast majority of form is indeed not « ready » for input, requiring users to go through hoops to fill them. And that work is done again by the next person.
- gpvos 6y agoI wasn't referring to any problem. Again, all those PDFs I wrote about are intended for reading only; no filling in, signing or other form of interaction other than reading letters that form words on a page is involved in any way, and that is entirely fine and how it should be, so both the PDF itself and a PDF reader that has no form-filling functionality would be entirely fit for purpose (notice the word "reader").
- nip 6y agoIn that case, all is well indeed. The problem I was referring to, is when one is expected to fill a PDF that was not built to be filled, such as the scan of a paper form.