© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Hello again,
I don't think the question is simple as there is a lot of context to this. When Poppler's API was conceived, PostScript was the standard format used for printing under Linux and other Unix-like systems. When qpdfview was conceived, this had already changed and PDF was declared as the default format for CUPS-based printing workflows which I would argue has more or less happened by now. (IIRC, printing a PostScript using a contemporary driverless CUPS setups will actually convert it to PDF before rasterizing it into a device-specific manner.)
Therefore, I decided from the start, that qpdfview would not convert PDF into PostScript for printing, but rather hand over the PDF file directly to CUPS which could then process it without loss of quality using e.g. tools like qpdf. I would like to stick to that decision as I see no technical reason why it should not work. The problem is mainly an organizational one of getting the patch into shape, merged, released and then using it in qpdfview.
Regards,
Adam