Re: [Printing-architecture] PDFio: Replaced QPDF by PDFio in libcupsfilters as GSoC project?
Alex Korobkin <[email protected]> Mon, 11 Dec 2023 11:12:12 -0500
| Newsgroups | dev.linux.lists.printing-architecture |
|---|---|
| Message-ID | <CA+3RNfgm8TtZFAoJP5+WZuH698VsDvgBMx1XV=DciLdTiswFrQ@mail.gmail.com> |
Hello printing folks, If you don't mind, may I chime in from the user's perspective? As you know, there are lots of bad PDFs out there, and even if they represent only 0.1% of the total number of all PDFs that people print, one million print jobs turns into 1000 tickets about unprintable files. QPDF is extremely accommodating about it: no matter how bad a PDF is, it will try to recover and proceed. Over the last few years I filed numerous requests about handling some despicable PDFs, and all of them were accepted. How is PDFio with regards to handling bad PDFs? Is there any testing tool with PDFio compiled in that I can run against my corpus of bad PDFs to see how it would treat them? On Thu, Dec 7, 2023 at 8:58 AM Till Kamppeter <[email protected]> wrote: > Hi, > > Michael Sweet has closed the PDFio issue in which I ask for support of > PDF forms and annotations, telling that inside PDFio nothing further > needs to be done, that everything can be solved outside PDFio, by the > calling application. > > As we want to get rid of C++ in libcupsfilters I plan to let it use > PDFio where it is currently using QPDF. > > Mike, as you tell that PDFio is OK for handling PDF files with filled > forms/annotations, I want to post a GSoC project idea to switch over > libcupsfilters from using QPDF to PDFio. WDYT? Is this possible already? > Or are there still any features missing in PDFio? > > Till > _______________________________________________ > Printing-architecture mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture > -- -Alex