Skip to main content
Participating Frequently
July 15, 2009
Question

Printer rips through the whole document before it starts to print

  • July 15, 2009
  • 2 replies
  • 1254 views

Thank you everyone for the answers to my previous post. Another Postscript problem which we are now trying to solve,

is the following printer behaviour:  getting our postscript datastream, printer first goes through the whole document,

ripping every page (or so it seems) and only then it starts printing the first page and further. Our datastreams are usually

large, tens thousandth of pages, so it takes very long before a printer starts to print. What could cause such a behaviour?

Something at the end of the file, which interpreter needs to take into account? Some special settings at prologue?

Thank you in advance for your help,

Yuliana

This topic has been closed for replies.

2 replies

Participating Frequently
July 16, 2009

This behaviour is typical for devices which implement a PDF-only RIP and in addition some PostScript to

PDF converter (e. g. , Adobe's normalizer) to digest PostScript input. An example I had the "joy" of getting

experience with is Kodak's Nexpress.

Participating Frequently
July 16, 2009

Thank you for answers. Printers are all high-volume XEROX printers, different models. So, it is not

known that some unlucky Postscript code structuring or content can cause such a behaviour?

That is what I really need to know - can it be that we are doing something wrong, when producing

PS code...

Participating Frequently
July 16, 2009

In case of those Xerox production printers, they offer various output modes,

like first page up or last page up when duplex printing etc.. Depending on thie

selected output mode, the printing process may require to render the pages in

reverse order to achieve the requested output mode, though the PostScript

interpreter RIPs the job in the normal manner.

Dov Isaacs
Legend
July 15, 2009

What you describe is not normal behaviour for PostScript implementations and is not something that is a feature of the PostScript language. The interpreter does not attempt to process the entire job prior to passing any of the rendered pages off to be imaged.

You give no idea as to what type or brand of PostScript printer is exhibiting this behaviour, but the behaviour is likely type and/or model and/or vendor-specific. Contact the technical support group for your printer or RIP vendor for specific answers to this question.

          - Dov

- Dov Isaacs, former Adobe Principal Scientist (April 30, 1990 - May 30, 2021)