Skip to main content
Inspiring
June 22, 2012
Answered

FM10/Acrobat Pro 9 not honoring joboptions

  • June 22, 2012
  • 1 reply
  • 3938 views

We've recently started transitioning from FrameMaker 9 to 10, and have retained Acrobat 9 Pro Extended rather than moving to Acrobat X. On the surface, Save As PDF works fine, however we have a need to specify a custom .joboptions file for Distiller in order to enforce PDF version 1.4 (Acrobat 4.x) compatibily because many of our customers use very old versions of AcroRead.

Late last week one of our writers noticed that FM10 Save As PDF through Distiller 9 is producing PDF Version 1.6 (Acrobat 7.x) files. I've been beating my head against this all week to no avail: If I produce PDF from FM9 with Save As PDF, I get v1.4 PDF; if I use FM10, I get v1.6. I can print from FM10 to the Adobe PDF printer and get v1.3; I can drag a PostScript file from FM10 into Distiller and get v1.3 PDF. I can even grab the .tps file produced by FM10 Save As PDF and get v1.3 PDF by running it through Distiller 9... . In one experiment I specified a given font as "always embed" in the .joboptions, and it was not embedded.  The .joboptions just seems to be ignored for some reason.

I've tried deleting the Adobe PDF printer instance and doing a "repair" on Acrobat 9, to no avail.

Anyone know whether something's changed between FM9 and 10? It just seems as though something different is going on under the covers that's preventing Distiller from honoring our .joboptions file. The only theory that I have left is that FM10 has some hardcoded override in its call to Distiller... .

-Cory R. Carpenter

This topic has been closed for replies.
Correct answer former Cory R. Carpenter

Error7103: This FDK plugin puts a PostScript frame in the source to augment PDF page-numbering display, and also corrects named destination markers.  We could print to PS and distill, alternatively we can Save As PDF and optimize to PDF 1.4 in Acrobat, but each of these mean extra steps for our writers... .


Bingo!

Replacing AdobeFrameMaker10\fminit\fmpdfreflow.dll with the version from FrameMaker 9 makes the problem go away.  I don't yet know what other problems it might cause though... .

-Cory R. Carpenter

1 reply

Van Kurtz
Inspiring
June 25, 2012

I do not know what FrameMaker does when one selects Save as PDF. I would not know how to set the joboptions using that route.

BUT one can select the joboptions when PRINTING to the Adobe PDF printer. Be sure to do two things: in the print dialog, click the Setup button (next to the name of the printer, Adobe PDF) and select the joboptions file for the printer; then click PDF Setup, and in that dialog select the joboptions in the Settings tag.

Inspiring
June 25, 2012

As I mentioned in the orginal post, printing to Adobe PDF works as expected, as does running the temporary PostScript file through Distiller manually.  It's only Save As PDF that displays this problem.  (When you have Distiller installed, Save As PDF creates a temporary PostScript -- .tps -- file and hands it to Distiller.)

Unfortunately, part of our custom infrastructure depends on the FDK FA_Note_PreDistill notification, so printing to Adobe PDF is not sufficient to our needs.

An additional data point: The problem persists with Distiller X, further suggesting that the problem lies with FrameMaker 10.

-Cory R. Carpenter

Van Kurtz
Inspiring
June 26, 2012

I know nothing about the FDK and what you need it to do, so this may not help.

Have you tried starting Distiller and selecting the joboptions there. Once the joboptions are selected, leave Distiller running. Then try saving the Frame file as PDF. In the distant past, this was the only way of setting Distiller joboptions. Maybe the process will not create a new instance of Distiller but use the one running. Of course, this will not work if the joboptions have to change for each PDF created.