Damaged fonts, damaged system files, damaged printer drivers, insufficient hard disk space, network problems, or hardware problems commonly cause system-level problems. The following offending commands indicate a problem with any element or graphic:ĭo you receive the error from more than one application? If the same problem occurs from more than one application, the cause is most likely a problem at the system level.
#PS FILE VIEWER DOWNLOAD#
For example, in the printer's properties (Windows), click Advanced, then, in the Graphics section, change the TrueType Font option to Download as Softfont. Note: For font-related errors, try changing the font-related settings in the device driver. The following offending commands indicate a problem with specific text or a font element: See the "Troubleshooting Possible Causes for the PostScript Error" section to continue troubleshooting.įollowing are common offending commands, grouped by general cause.
#PS FILE VIEWER CODE#
In this case, your file contains PostScript code the PostScript interpreter can't recognize. The "PostScript Offending Command" section lists "" under the heading that indicates a problem with any element or file. For example, you could receive the PostScript error "%%%%." The "PostScript Error Types" section lists "undefined" under the "Errors that indicate unintelligible PostScript code" heading. Some PostScript errors don't help you determine a likely cause. You can also try printing the file to a printer with more memory. If you find a likely culprit, you can delete the graphic, reimport it, save it in different format, or simplify it (for example, reduce its dpi). You can then check graphics in your file to see if one or more is causing the problem. The likeliest source of bitmap data is a graphic in your file.
So, you have bitmap data that exceeds the printer's memory or PostScript language limit. The "PostScript Error Types" section lists "limitcheck" under the heading "Exceeds printer's memory or PostScript language limit." The "PostScript Offending Command" lists "image" under the heading that indicates a problem with bitmap data. You can then try to repair the problem.įor example, you could receive the PostScript error, "%%%%." Your first step is to locate "limitcheck" in the "PostScript Error Types" section. To begin troubleshooting, locate the error type and offending command in the "PostScript Error Types" and the "PostScript Offending Commands" parts of this document. The offending command is the last command the PostScript interpreter tried to process, "def," which defines a new word in the dictionary.Īfter you identify a specific PostScript error message, you can begin troubleshooting the cause. Some PostScript errors point you right to the cause of the problem, and some get you looking in the right direction.įor example, the PostScript error %%%% contains the PostScript error type "dictfull" and the offending command "def." The error type indicates that the dictionary contains the maximum number of entries. The offending command usually indicates the command that caused the problem. It also includes an offending command, which usually indicates the specific part of the PostScript code that the interpreter couldn't read. If your PostScript interpreter appears to process data but then stops, a PostScript error could have occurred.Ī PostScript error message includes a PostScript error type, which defines the type of error it is. An error can also occur if the file's PostScript code exceeds one or more of the limits in the PostScript page description language. A PostScript error occurs when the PostScript interpreter can't read the file's PostScript code.
You can receive a PostScript error when sending a file to a PostScript interpreter (for example, a printer, Acrobat Distiller).
0 kommentar(er)
