I do have a laser printer, who is, for a reason I did not figured out know for 4 years, not printing every 3rd or 4th PDF I sent him.
I bought a second printer, to solve the problem so far, but before that, I was able to force the print by using PostScript instead.
PostScript is still the easiest way to make a networked printer work with any OS. [quote=“Ulli, post:2, topic:29765, full:true”]
I do have a laser printer, who is, for a reason I did not figured out know for 4 years, not printing every 3rd or 4th PDF I sent him…
I have a laser that goes crazy every 3rd or 4th print and gives me gibberish. When using the “printer driver for that model”. Now I have it on the network as “Generic PostScript printer” and…zero issues.
PostScript is still the best route if you want a network printer to work with any OS from the last 40 and probably the next 40 years.
I’ve programmatically generated PostScript files within the past ten years, before I retired, and had done so at least as far back as the late 1980s. There were two reasons – I could print directly to the printer (which “speaks” PostScript) without needing some intervening program, and PostScript is a fine language for generating graphs and charts from dynamically changing data.
This ability had me using Apple laser printers back in the day, when I didn’t have a Mac to use until many years later.
I guess it’s mostly still around out of inertia. The library function is available, it works perfectly, so why not offer a menu option for anyone who might still need it? Keeping it in is also avoiding any press outlets covering the inevtiable “Postscript Gate” that would follow its removal
There are probably good use cases still that I am simply not aware of as well.