One solution is to install cups-pdf. It adds a virtual printer that writes PDF files. There are several tutorials on the web about how to install and configure it; since I use Gentoo, I've read Gentoo-wiki, which also mentions Sabayon wiki.
cups-pdf virtual printer has a configuration file in /etc/cups/cups-pdf.conf
, and by default all PDF files are written to /var/spool/cups-pdf/${USER}
.
(NB: On Ubuntu it writes to ~/PDF/)
There are a few limitations, though:
Since there is only one configuration file, multiple PDF printers will save to the same directory.
It is impossible to print "raw" data (using, for instance, lpr -o raw
). Even sending a PDF file as a raw job will not work. Raw print jobs will generate a blank PDF file with just an empty page.
Even with these limitations, it works perfectly for my needs.
Footnote: if the user is using Gnome, or printing through a GTK+ application, then there is already a "Print to File" pseudo-printer at the print dialog. Thus, why should the user still want to add a virtual PDF printer? Here are a few reasons:
- That "Print to File" is specific to GTK+, and is not available for non-GTK+ applications. (maybe KDE has a similar feature, but I'm not sure)
- It makes possible to generate a PDF from Flash "applications" that were designed for printing. For instance, the PocketMod.
- Adding a virtual printer to CUPS makes it possible to test printing using shell scripts or other software that talks directly with CUPS. This is specially useful for developers while testing their applications.
- It is possible to "share" this virtual printer with the local network. Not exactly useful, but possible.
- It is possible to attach a post-processing command to be executed right after the PDF file has been saved.
1
See also creating a dummy printer.
– Wilfred Hughes – 2015-01-22T10:20:57.930isnt this correct "lpadmin -p lp0 -E -v /dev/null -m raw" – Ashika Umanga Umagiliya – 2012-07-30T05:09:18.760