[EMAIL PROTECTED] wrote: > Dear Peter, > > As the lp concept of printing is to temporarily capture a file (frequently > to the hard drive) as it is generated by an application, and then send it to > a defined destination once the file is completely created, it is possible > for system issues (such as number of open files) to impede the proper > creation of the file to be printed. > Don't forget also, that modern Unix (and linux especially) seems to assume that all printers are postscript. That really cheeses me off, in that it's a right pain if you actually want to control the printer yourself for some reason (like in this case, sending HP control sequences to an HP printer!)
It's pretty much a certainty that, by default, this print job is being spooled throught ghostscript. Which will detect it is a text file, and wrap it in the necessary postscript code, fooling the printer into treating it as postscript (if it's a postscript printer) or ghostscript will mangle it itself (if it's not a postscript printer). To my mind, modern linux printing is one of the worst bits of linux. It tries to force you to use CUPS (totally ignoring the linux mantra of "choice"); while CUPS, even by the standard of Unix, is exceptionally user-vicious. Just read ESR's "Aunt Tilley" diatribe about CUPS ... My worst experience is where I tried to connect to a network printer. I wanted to tell it where the printer was, so I told it to NOT do a network scan. Next thing I knew, the configuration utility had started (uninteruptably) scanning the network looking for printers ... Cheers, Wol ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
