Postscript Error Using Unix
Contents |
The error can be caused by numerous things such as missing dictionaries, imported graphics, data corruption, communication problems or error undefined offending command stack missing PostScript header information. General solutions Some offending commands indicate a xerox error undefined offending command stack possible problem with the driver settings or printer support files. Updating drivers or switching to an
Pdf Error 19 Postscript Error Undefined
alternative driver might solve the problem. You can also try to copy and paste all elements to a new file. If the document was converted from
Error: Syntax Error Offending Command: Stack
a previous version of an application, try printing again from that version. A strange word as an offending command: Sometimes a RIP generates an ‘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 error typecheck offending command image 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 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 ‘
Please make sure to follow the naming policy. Dividing books into smaller sections can provide more focus and allow each one to do one thing well, which benefits everyone. You can ask for help in dividing this book in the assistance reading room.
Error Unregistered Offending Command Show
This FAQ covers PostScript language and Ghostscript software suite, as the most common free PostScript interpreter. Contents error syntax error offending command nostringval 1 General 1.1 PostScript resources 1.2 How to report a PostScript error? 1.3 Who can help me? 2 Using PostScript 2.1 Do I need a error unregistered offending command xshow PostScript printer? 2.2 How to create a PS file? 2.3 How to send a PS file to a printer? 2.4 What is the best way to view a PS file on the screen? 2.5 How to send a binary PostScript file https://www.prepressure.com/postscript/troubleshooting/errors/undefined to an ASCII-only printer? 2.6 How to print an EPS file? 2.7 How to check whether a PostScript file is valid? 2.8 How to count pages in a PS file? 2.9 How to determine which pages are color and which are monochrome? 2.10 How to print only some pages from a PS file? 2.11 How to rearrange pages of a PS file for printing a brochure? 2.12 Why does my PS driver generate color drawings but grayscale images? 2.13 How to recombine https://en.wikibooks.org/wiki/PostScript_FAQ plates in preseparated PostScript file? 2.14 How to remove black frames around n-up pages? 2.15 How to print A4 on US Letter or vice versa? 2.16 How to extract figures from PostScript files? 2.17 How to change color PostScript to black-and-white?* 2.18 How to tweak RGB to CMYK conversion but leave other objects intact? 2.19 How to get date and time? 3 Programming PostScript 3.1 How to edit a PS file? 3.2 How to create a PS form and populate it from a database? 3.3 How to concatenate several PS files? 3.4 How to print accented characters? 3.5 How to justify text in PostScript? 3.6 How to place several copies of a picture? 3.7 How to redefine an operator? 3.8 How to concatenate strings? 3.9 Where are min and max functions? 3.10 How to sort an array? 3.11 How can I display Copyright and other symbols? 3.12 Where can I get more examples of PostScript code? 3.13 How to debug a PostScript program? 3.14 How to include an EPS file? 3.15 Does PostScript support unicode for CJK fonts? 4 Known errors 4.1 undefined in /RD 4.2 PageMaker 7.0 page information fails in level 1 mode 5 Using Ghostscript 5.1 What is Ghostscript and where can I get it? 5.2 How to create compressed CMYK TIFF? 5.3 What CJK fonts work on Ghostscript? 5.4 How to avoid JPEG compression in PDF? 5.5 Ghostscript fails with /invalidfont in findfont? 5.6 How to create a semi-transparent object? 5.7 PostScr
formats Bounding box output Choosing paper size Changing the installed default paper size How Ghostscript finds files Finding PostScript Level 2 resources Font lookup Temporary files http://ghostscript.com/doc/7.07/Use.htm CID font substitution Summary of environment variables Using Ghostscript with EPS files Using Ghostscript http://www.ghostscript.com/doc/current/Ps2pdf.htm with PDF files PDF files from standard input Switches for PDF files Problems interpreting a PDF file Notes on specific platforms Unix VMS Using X Windows on VMS MS Windows MS-DOS X Windows X resources Working around bugs in X servers X fonts Using Ghostscript fonts on X displays X device parameters SCO Unix offending command Switches General switches Input control File searching Setting parameters Suppress messages Parameter switches (-d and -s) Rendering parameters Page parameters Font-related parameters Interaction-related parameters Device and output selection parameters Other parameters Improving performance Debugging Appendix: Paper sizes known to Ghostscript Appendix: X default font mappings Standard X servers Regular fonts Symbol fonts Dingbat fonts Sun OpenWindows For other information, see the Ghostscript overview, the new user's documentation error undefined offending on previewers and, if necessary, how to install Ghostscript. Invoking Ghostscript The command line to invoke Ghostscript is essentially the same on all systems, although the name of the executable program itself may differ among systems. For instance, to invoke Ghostscript on Unix: gs [switches] {filename 1} ... [switches] {filename N} ... Ghostscript's name on different systems System Ghostscript's name Unix gs VMS gs DOS & MS Windows 3 gs386 MS Windows 95/98 gswin32 MS Windows 95/98 command line gswin32c OS/2 gsos2 Note, though, that on a system with a windowed graphical user interface, it's common to use Ghostscript through a previewer, so you should read the section about previewers in the documentation for new users. Ghostscript is capable of interpreting PostScript, encapsulated PostScript (EPS), DOS EPS (EPSF), and -- if the executable was built for it -- Adobe Portable Document Format (PDF). The interpreter reads and executes the files in sequence, using the method described under "File searching" to find them. After doing this, it reads further lines of PostScript language commands from the primary input stream, normally the keyboard, interpreting each line separately. To quit the interpreter, type "quit". The interpreter also quits gracefully if it encounters
problems Comparison of ps2pdf and Acrobat Distiller Acknowledgments For other information, see the Ghostscript overview. Overview ps2pdf is a work-alike for nearly all the functionality (but not the user interface) of Adobe's AcrobatTM DistillerTM product: it converts PostScript files to Portable Document Format (PDF) files. ps2pdf is implemented as a very small command script (batch file) that invokes Ghostscript, selecting a special "output device" called pdfwrite. Usage The usage for ps2pdf is ps2pdf [options] input.[e]ps output.pdf or, on Unix systems and some versions of Windows NT and OS/2 ps2pdf input.[e]ps which is equivalent to ps2pdf input.[e]ps input.pdf There are actually several different ps2pdf* scripts: the name ps2pdf above refers to any of them. ps2pdf12 produces PDF 1.2 output (Acrobat 3-and-later compatible). ps2pdf13 produces PDF 1.3 output (Acrobat 4-and-later compatible). ps2pdf14 produces PDF 1.4 output (Acrobat 5-and-later compatible). ps2pdf per se currently produces PDF 1.4 output. However, this may change in the future. If you care about compatibility with a specific output level,use the -dCompatibilityLevel=1.x switch in the command line, or one of the specific version aliases ps2pdf12, ps2pdf13, or ps2pdf14. Note that if you specify a value for PDFSETTINGS, this chooses PDF 1.3 or 1.4 output depending on the value of PDFSETTINGS: this overrides the output format specified by the script name. You can still specify the output format by using -dCompatibilityLevel= after -dPDFSETTINGS=. All of these scripts actually call a script named ps2pdfwr or ps2pdfxx. The Unix ps2pdfwr script assumes that the Ghostscript executable is named gs; it is unlikely that you will need to change this. The DOS and MS Windows ps2pdfxx.bat script uses the value of the GSC environment variable, if defined, as the name of the executable; otherwise the script assumes the executable is named gswin32c. So in these environments, if the executable has a different name, you must set GSC to the name of the executable. Ordinarily a single PDF file will be written that includes all input files (concatenated), but if the OutputFile is changed then the current pages will be written and a new PDF file will be started. Note that the OutputFi