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.
#Pdftops ps to pdf code#
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.
Which font details can you tell us about your resulting PDFs? (Try pdffonts your.pdf to find out - pdffonts is also part of the Poppler utils you mentioned.You can receive a PostScript error when sending a file to a PostScript interpreter (for example, a printer, Acrobat Distiller).
#Pdftops ps to pdf pdf#
One likely cause for your inability to copy text from the PDF could be the font type (and encoding) that ended up being used and embedded in your PDF file. So, which is the version of Ghostscript installed on your system? (Remember, ps2pdf calls Ghostscript, it will not work without a locally installed gs executable.) Thirdly, Ghostscript gained a lot of additional power and control, and had a few bugs or weak spots removed over the last few years when it comes to outputing PDF. Second, without exactly knowing how exactly your PS input file is conditioned, it is difficult to give you good advice: Does your PS have embedded the fonts it uses? Which type of fonts are they? etc. (You can tweak a few parameters with ps2pdf - but then you are already so much closer to run the real Ghostscript command already.) ps2pdf it takes away a lot of potential control you could have if you used Ghostscript. Ghostscript has many more options, but it is more difficult to learn. Is that correct?)įirst of all, most likely your ps2pdf is only a shellscript, which internally uses a Ghostscript command with some default parameters to do the real work. (I'm assuming your phrase of vice-versa isn't meant to point to a 'round-trip' conversion of the very same file, but the general direction of conversion for any PS file. I'm just covering the PS->PDF conversion.
0 kommentar(er)
