On Tue, Mar 23, 2004 at 12:05:41PM +1100, Wolfgang Gill wrote: > > > -----Original Message----- > > It's not the printing that is slow. It's the generation of the > postscript to send to the spooler. The postscript file is ~22MB in size > and takes minutes to generate, evolution being totally unresponsive the > whole time, not even redrawing its windows. The same thing happens if I > print Generic Postscipt to a file. If I then run it through ps2ps it > gets distilled down to 18k!!! The postscript file evolution is > generating is over 1200 times the size it should be. > > -Steve > > I guess in a way that is what I mean. The TP drivers talk to the printer > natively. Where Cups generates a Postscript format and then sends it to the > printer. I'm in the office right now, and don't have Evolution configured, > else I'd try it here. I've always found the Cups drivers to be slow > regardless of the type of printer. > > Just as a test here at the office, we have a HP LJ4100TDN and I noticed the > driver was configured for Postscript. I sent it a 12 page document and it > took around 2 minutes to print the first page. I then changed it to > gimp-print, and it was instant. That might help speed things up a bit. > > Wolf > I agree that a printer that is printing directly to a printer should never be configured as postscript. Use the driver for the printer. Now for pronting through a server the postscript driver works well. -- ------------------------------------------- Aaron Konstam Computer Science Trinity University One Trinity Place. San Antonio, TX 78212-7200 telephone: (210)-999-7484 email:akonstam@xxxxxxxxxxx -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
