Comment 19 for bug 820820

Revision history for this message
Martin-Éric Racine (q-funk) wrote :

Upstream says that he never noticed how those recent internal changes in CUPS could make the production of PDF documents much easier than before and no longer require Ghostscript by default.

What he is likely to do is to fix outstanding bugs within the 2.6 series and then, if his initial testing in his work environment is conclusive, fork the code to a 3.0 series that specifically depend upon recent upstream CUPS features for producing the PDF documents, all while retaining the existing configuration file format.

Upstream would however like to point out that, at his workplace, CUPS-PDF is often used to produce reports by automated means e.g. by networked laboratory equipment, so his code cannot make the assumption that CUPS-PDF would be used within a desktop environment or even from a Free Software printing client.

In any case, he cannot return to these issues until his Christmas vacations. Until then, if we have any patch to propose him, that could perhaps help speed up the migration process.