(with none of the modifications you want yet). Each result should for now be a PostScript file. The 2dir backend now will write all output to directory /tmp/pdfqueue/ and it will use a uniq name for each job. Make sure when copying that you get the line endings right (Unix-like). That one can be copied from this website: KDE Printing Developer Tools Wiki. Initially, use the (educational) CUPS backend named 2dir. (A PostScript PPD is one which does not contain any *cupsFilter. But I recommend to use a PostScript driver/PPD.
#Print conversation in mac to pdf driver driver#
Set up a print queue with any driver you like. If anyone can get either of these to work on a mac through the terminal, please let me know step-by-step how you did it. And if anyone is looking for a user-end PDF-printer, this cups-pdf-for-mac-os-x is one that works through the installer, however I have the same issue of no file appearing in the indicated directory when I download the source and follow the instructions in the readme. I've worked through this printing with CUPS tutorial and seem to get everything set up okay, but the file never seems to appear in the appropriate temporary location.
#Print conversation in mac to pdf driver pdf#
I guess my questions are: how do I add a virtual "printer" driver for the user that will launch the application I've been developing that will make the PDF (or make the PDF and launch my application with references to the newly generated PDF)? How do I interface with CUPS to generate the PDF? I'm not sure I'm being clear, so let me know if more information would be helpful.
I want to add a print option that prints whatever the user's document is to a PDF and adds some headers before sending it off to a device.
0 kommentar(er)
