A pdfmark is a small piece of code that an application can include in its print files to tell Acrobat Distiller how the handle a specific aspect of the creation of a PDF file. For example: using pdfmarks, an application can instruct Distiller to add a hotlink to a small piece of text in its file, so that if you click on that word in the PDF, a web browser like Firefox opens a web page.
Errors that contain an offending command ‘pdfmark’ point to some kind of problem in processing these pdfmarks. The error should only pop up in Distiller or equivalent programs because it makes no sense trying to send PDFmarks to a normal RIP.
Solving this kind of error should not be to difficult: disable pdfmark creation in the originating application. The only problem is that this option may be hidden under some exotic description.
- Take for example FrameMaker 7. It has a known problem with files that fail while creating PDFs or distilling PS files with tagged PDF information. The error is (%%[ Error: undefined; Offending Command: pdfmark; ErrorInfo: StRetrieve P127021 ]%% Stack: /StRetrieve) … As a workaround, turn off ‘Generate Tagged PDF’ in the PDF Setup menu.
- The same is true in FrameMaker 6 which can generate errors looking like this: %%[ Error: typecheck; Offending Command: pdfmark; ErrorInfo: PUT _objdef ]%% . Turning off ‘Generate Tagged PDF’ in the PDF Setup menu also gets rid of this error.
Yet another FrameMaker 6 or 7 tip: instead of printing to a PostScript file and then processing that file with Distiller, print to the Adobe PDF printer.