[Gnome-print] Re: [Gimp-print-devel] An introduction to gnome-print (fwd)
- From: Miguel de Icaza <miguel helixcode com>
- To: Robert L Krawitz <rlk alum mit edu>
- Cc: neumanns uni-duesseldorf de, gnome-print helixcode com, rlk tiac net, mike easysw com
- Subject: [Gnome-print] Re: [Gimp-print-devel] An introduction to gnome-print (fwd)
- Date: 31 May 2000 20:39:29 -0400
> As an application programmer, you may not. As a system administrator,
> you certainly do. I've routinely generated single page print files
> that exceed 50 MB. I have a 2.5 MB Postscript file -- an image --
> that bloats out to 50 MB when rendered as a high quality escp2/raster
> image file for the 870. My resume -- a 17K Postscript file -- will
> render into a multi-megabyte (probably about 10 MB) file as an Epson
> print file. Now, suppose I'm printing a 100 page Postscript document
> that's about 1 MB of Postscript. Am I better off sending one MB or 1
> GB over the network and store it in a spool directory?
Those numbers do not match what Chema has been getting from his PCL
driver. It matches the lame case, but not any case with the smallest
ammount of optimization.
Anyways, that is not the point. We have a Postscript driver, want to
use that instead of an Epson, click on "driver" and select
"Postscript", then click "Print".
Am I missing something?
> Now, imagine that I have 10 printers, and on average they have 5 such
> jobs queued. NOW do you see what we're talking about? It most
> certainly DOES matter from a system perspective where the rendering is
> done!
Really irrelevant. According to Chema's data it would be around a 6
meg file, so 60 megs on the queue. I though you were into high-end
servers :-)
Miguel.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]