Post Script Error Definitions
Contents |
to solve such an error? Why do PostScript errors even exist? What is a PostScript error? Every PostScript device contains a RIP (or Raster Image Processor). This is a computer that translates the pages you want to print from PostScript into error undefined offending command stack a format that the PostScript device understands. If the RIP encounters an error while performing this
Error Rangecheck Offending Command Image
translation, it returns a PostScript error message to the device that send the file. The error can be caused by bugs in the
Xerox Error Undefined Offending Command Stack
PostScript code itself, data corruption, limitations of the RIP and PostScript device processing the file, incompatibilities between different devices or applications, bad karma,… What do PostScript errors look like? A PostScript error has two parts: the error and
Error Syntaxerror Offending Command
the offending command. Take a look at a typical PostScript error: %%[Error: limitcheck; Offending command: image ]%% The error tells you exactly what problem the RIP encountered while processing your file. In the example, it is a limitcheck. Thankfully, there are a limited number of errors that can occur on PostScript devices. I think there are about 30 or so but I could be wrong. The offending command signals what specific PostScript command (or operator as they are error unregistered offending command show called) was being processed by the RIP when the error occurred. In some cases, the offending command doesn't really look like a command but it is a series of random characters. This means the RIP has encountered some information in your printfile that it considers to be a PostScript operator but is not. This can happen with corrupted images, bad network connections and so on. Can PostScript errors be solved? Well, this website wouldn't make much sense if that wasn't possible. Of course, it helps if you know the famous Adobe Red Book by heart. But knowledge of the PostScript language is no prerequisite for troubleshooting PostScript errors. In reality, it is often a matter of luck. Errors caused by bugs in applications or drivers are sometimes well documented and easy to resolve. The same is true for errors caused by limitations or bugs in the software of the RIP itself. Errors caused by corrupted data can be tricky to troubleshoot. The same is true for PostScript errors caused by incompatibilities between different applications and RIPs. Why do PostScript errors even exist? In a perfect world, error messages wouldn't exist. But unfortunately we are stuck in a real world and errors usually occur on big jobs that are already past their deadline. Much of the problems with PostScript are related to the fact that PostScript is really a programming lang
The error can be caused by numerous things such as missing dictionaries, imported graphics, data corruption, communication problems or missing PostScript header information. General solutions Some offending commands indicate a possible error syntax error offending command nostringval problem with the driver settings or printer support files. Updating drivers or switching error unregistered offending command xshow to an alternative driver might solve the problem. You can also try to copy and paste all elements to a error undefined offending command g2ubegin new file. If the document was converted from a previous version of an application, try printing again from that version. A strange word as an offending command: Sometimes a RIP generates an https://www.prepressure.com/postscript/troubleshooting/basics ‘undefined' PostScript error, with an offending command ‘bspt' or another randomly chosen kind of technical term like ‘fob' of ‘xtrfx'. Such errors indicate that the RIP tries to execute a command that has not been defined in the PostScript file. In a lot of cases, PostScript error "undefined" issues are caused by incorrect drivers: PostScript drivers that are corrupted or that are vendor-specific (eg you try https://www.prepressure.com/postscript/troubleshooting/errors/undefined printing to a Tectronix printer using an HP driver) PPDs that are too old or too new. PPDs that should be used for another device. Some applications that put themselves in-between your application and the RIP can also cause this kind of a problem: try printing without passing through a spooler or OPI-system. Use another imposition software or try to avoid using your trapping software. Sometimes the name of the offending command indicates which application is causing the problem. I remember a customer who by accident had deleted a number of PostScript files from his Preps folder. Subsequently Preps kept generating ‘undefined' errors because its printfiles lacked the necessary code. We found this rather quick because the offending command started with ‘SS' or so, something that we linked to ScenicSoft, the makers of Preps. Specific errors PostScript error undefined offending command D On Macs running Leopard the above error can pop up with a wide range of printers including the HP LaserJet 1200 and HP PSC 1610xi. Installing and using a Gutenprint driver seems to resolve the problem. An alternative solution is to deactivate error reporting, as documented in this procedure on disabling PostScrip
reliable sources. Unsourced material may be challenged and removed. (June 2009) (Learn how and when to remove this template message) PostScript Paradigm Multi-paradigm: stack-based, procedural Designedby John Warnock, Chuck Geschke, Doug Brotz, Ed Taft, Bill Paxton Developer Adobe Systems https://en.wikipedia.org/wiki/PostScript Firstappeared 1982; 34years ago(1982) Stable release PostScript 3 / 1997; 19years ago(1997) Typing discipline dynamic, strong Major implementations Adobe PostScript, TrueImage, Ghostscript Influenced by Interpress, Lisp Influenced PDF PostScript Filename extension .ps Internet mediatype application/postscript Uniform Type Identifier(UTI) com.adobe.postscript Magic number %! Developedby Adobe Systems Type of format printing file format Extendedto Encapsulated PostScript PostScript (PS) is a computer language for creating vector graphics. It is a dynamically typed, concatenative offending command programming language and was created at Adobe Systems by John Warnock, Charles Geschke, Doug Brotz, Ed Taft and Bill Paxton from 1982 to 1984. It is used as a page description language in the electronic publishing and desktop publishing. Contents 1 History 1.1 PostScript Level 1 1.2 PostScript Level 2 1.3 PostScript 3 2 Use in printing 2.1 Before PostScript 2.2 PostScript printing 2.3 Font handling 2.4 Other implementations 3 Use error undefined offending as a display system 4 The language 4.1 "Hello world" 4.2 Units of length 5 See also 6 Notes 7 References 8 External links History[edit] The concepts of the PostScript language were seeded in 1976 when John Warnock was working at Evans & Sutherland, a computer graphics company. At that time John Warnock was developing an interpreter for a large three-dimensional graphics database of New York harbor. Warnock conceived the Design System language to process the graphics. Concurrently, researchers at Xerox PARC had developed the first laser printer and had recognized the need for a standard means of defining page images. In 1975-76 Bob Sproull and William Newman developed the Press format, which was eventually used in the Xerox Star system to drive laser printers. But Press, a data format rather than a language, lacked flexibility, and PARC mounted the Interpress effort to create a successor. In 1978 Evans & Sutherland asked Warnock to move from the San Francisco Bay Area to their main headquarters in Utah, but he was not interested in moving. He then joined Xerox PARC to work with Martin Newell. They rewrote Design System to create J & M (for "John and Martin") which was used for VLSI design and the investigation of type
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 08:42:28 GMT by s_wx1196 (squid/3.5.20)