ColorSpan Legacy Print Server - Troubleshooting PostScript Errors

Introduction

When images and publications do not print as expected or do not print at all due to a PostScript error,

there can be a variety reasons. For example, the publication may be unnecessarily complex, composed

with corrupt data or even contain a poorly constructed font. Here are some suggestions to help

minimize the chance of having problems with printing your files. Also included are some techniques

used by industry experts to troubleshoot PostScript errors.

What causes a PostScript error?

PostScript is a programming language used to describe pages to be printed. In general, PostScript

errors occur when the PostScript interpreter cannot continue to process an image due to some problem

in the file. The interpreter may not recognize a specific Post-Script command, or the PostScript

command may exceed some limit of the interpreter.

What is a PostScript error message?

There are two parts to a PostScript error message: the error and the offending command. Although

they vary slightly among the different printer families (or different Post-Script interpreters), PostScript

errors generally look something like the following:

Error: [error name]; OffendingCommand: [bad command].

The information in the error message tells you what the PostScript error is (the error name) and what

PostScript command caused it (the offending command).

Note: If you are printing to a Legacy ColorMark Server, you can obtain PostScript error information by

opening the tracking log record for the job, and selecting ‘PS Output.’

Steps to Take After Finding the PostScript Error

Having a printout of the PostScript error can help isolate which portion of the publication contains the

offending object. It could be anything from a corrupted graphic to a complex clipping path to a damaged

font. Generally speaking, the more complex an element is, the more likely it is to be the source of the

problem. Your choice of output devices may affect whether or not a file will print. Since implementation

limits vary from output device to output device, the potential for PostScript errors also varies: a laser

printer that prints in shades of gray may not report an error that is reported on a more demanding color

output device.

Isolating the Source of the Error

There’s no magical way to tell which component of a document is causing the problem; however, there

are elements that are more likely to result in problems with ALL Post-Script interpreters. This fax also

will explain some errors and reasons for the errors to occur. The following is a list of common

troublemakers for all PostScript interpreters:

a. Nested EPS images, i.e, placing one EPS image on top of another and then saving both as an

EPS.

b. Complex clipping paths such as a mask for a graphic.

c. Fonts of questionable quality or fonts that have been converted from some other format

d. Color gradations

e. Blends with a large number of steps

f. Images that are rotated after being placed in a publication, especially when combined with

elements from above

g. Many different fonts on the same page

h. Vector artwork with numerous points in its curves

i. Complex fill patterns