PostScript FAQ/Known errors

Known errors

This is a list of work-arounds for PostScript errors in proprietary software. Bugs in free software should be reported to the program maintainer and fixed. The fixes posted here try go to the root of the problem. This database of PostScript errors gives an insight into the user's perception of PostScript errors.

undefined in /RD

This problem can be caused by incorrect embedded Type 1 fonts in PDF files or PostScript files generated from PDF. Adobe Acrobat doesn't use procedures defined in Type 1 font and the problem may be left unnoticed.

Define the following procedures in userdict to work around the problem.

 /RD { string currentfile exch readstring pop } executeonly def
 /ND { noaccess def } executeonly def
 /NP { noaccess put } executeonly def

PageMaker 7.0 page information fails in level 1 mode

PageMaker 7.0 with Page Information printer's mark set ON generates incorrect PostScript file in level 1 mode. The file fails with invalidaccess in get or typecheck in get on any interpreter, regardless of the level.

The problem is caused by interaction between PageMaker code and Windows driver code. To print separations Adobe redefines a few operators, including setcolorspace and uses them even in level 1 mode. PostScript driver assumes that setcolorspace has no place in Level 1 PostScript and redefines it as {pop} as a precaution, erasing the earlier definition.

 /setcolorspace{!}b 

To fix the file this definition should be removed or commented out.