Avoiding Critical PostScript Driver Settings on the Client
Printing works, but there are still problems. Most jobs print well, some do not print at all. Some jobs have
problems with fonts, which do not look very good. Some jobs print fast and some are dead-slow. Many of these
problems can be greatly reduced or even completely eliminated if you follow a few guidelines. Remember, if
your print device is not PostScript-enabled, you are treating your Ghostscript installation on your CUPS host
with the output your client driver settings produce. Treat it well:
Avoid the PostScript Output Option: Optimize for Speed setting. Use the Optimize for Portability instead
(Adobe PostScript driver).
Don't use the Page Independence: NO setting. Instead, use Page Independence: YES (CUPS PostScript Driver).
Recommended is the True Type Font Downloading Option: Native True Type over Automatic and Outline;
you should by all means avoid Bitmap (Adobe PostScript Driver).
Choose True Type Font: Download as Softfont into Printer over the default Replace by Device
Font (for exotic fonts, you may need to change it back to get a printout at all; Adobe).
Sometimes you can choose PostScript Language Level: in case of problems try 2
instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well; Adobe).
Say Yes to PostScript Error Handler (Adobe).