Skip to main content
L
lsramos
New Participant
January 18, 2023
Question

Problems printing book to PS and PDF

  • January 18, 2023
  • 5 replies
  • 1833 views

We recently had to update our FrameMaker generated user guide (over 500 pages, 100s of graphics) and updated to a newer version of FrameMaker to do so (FM 2017 release). Now, we are finally at the point where we need to publish the PDF. And have run across a number of issues.

 

1. Save as PDF fails. Always. It spins for minutes on end, then FM crashes, leaving all .fm files locked. Sometimes a .tps file is created.

2. Print Book has had issues as well. There are a number of settings that MUST be set before this (sort of) succeeds. A 3-year old discussion on this forum revealed many insights.

(see: https://community.adobe.com/t5/framemaker-discussions/unable-to-save-as-pdf-in-framemaker-2017/td-p/10373159)

3. Print Book and Print to File as .ps file fails to generate the .ps file IF the destination is on a mapped drive. We got around this by saving to the Desktop, then distilling the .ps file there.

 

So, we are largely back in business. One issue remains. In the past, the PDF file when viewed in Acrobat Reader shows vanilla page numbers. To make this more user friendly, we had been using PageLabeler to make the page numbers appear as they do on the page, such as 12-34 (that is, chapternumber-pagenumber). Apparently, Carmen Publishing no longer produces PageLabeler and our old version does not work with the newer version of FrameMaker.

Is it possible to create a 'friendly' to Acrobat PDF file that will show us the actual hyphenated page numbers in the ribbon ("To go to a specific page, specify the page number and press Enter. ")?

Thanks,
Scott

 

 

    This topic has been closed for replies.

    5 replies

    frameexpert
    frameexpert
    Adobe Expert
    January 19, 2023

    Regarding PageLabeler: the ExtendScript version of PageLabeler should work with any version of FrameMaker, including the latest. However, with the new PDF engine, Distiller is not used to create PDFs by default. Distiller allowed PageLabeler to use Pdfmark commands in Postscript text frames to insert "friendly" FrameMaker page numbers in the PDF. That was the original purpose of FrameMaker's Postscript text frames: to inject Postscript code into your FrameMaker documents so you could provide features that FrameMaker didn't have natively. The primary use case was adding Acrobat features to a FrameMaker document so you wouldn't have to post-process your PDF everytime it was created.

     

    Pdfmark is an extension to the Postscript language that allows Acrobat features to be added to a PDF through the distilling process. We provided a large number of solutions over the years that used Pdfmark commands to crop pages, add custom bookmarks, create buttons and form fields, etc. Pdfmark was the basis of MicroType's brilliant TimeSavers software, written by Shlomo Perets. TimeSavers allowed you to use FrameMaker markers with a simpler syntax, instead of Postscript text frames with raw Pdfmark commands.

     

    When FrameMaker moved away from Distiller, this powerful capacity was mostly lost, in spite of pleas by me and others. Note that there are workarounds that will allow you to use Distiller with later versions of FrameMaker. But these negate the FrameMaker-to-PDF speed increases that were introduced with the new PDF engine.

     

    Adobe was forced to acknowledge this loss when a FrameMaker Publishing Server client need to do some custom page cropping. Because a simple Pdfmark solution was no longer practical, they added an undocumented way of cropping via a hidden property that could be accessed via ExtendScript and the FDK. My hope is that they will provide a way to insert more custom PDF features in FrameMaker (custom bookmarks, buttons, form fields, etc.) that will work with the faster PDF engine.

    L
    lsramosAuthor
    New Participant
    January 19, 2023

    Is it possible to obtain the ExtendScript version of PageLabeler? I don't see it on the Carmen Publishing site.

    We could re-use the existing postscript text frame generated from our (much) older version of PageLabeler, but still need a means to map the final document page numbers to the chapter starting pages.

    frameexpert
    frameexpert
    Adobe Expert
    January 19, 2023

    Please contact me offlist. Thank you.

    K.Daube
    K.Daube
    Brainiac
    January 19, 2023

    «updated to a newer version of FrameMaker to do so (FM 2017 release).»

    Well with FM-15 (aka 2019 release) a new method of producing PDF was introduced, which is to be set up in the Publish Panel and can then be also used via Save As PDF.

    BTW the newest version of FM is 17.0.1. 305 (2022 release) ...

    M
    mk-will
    Inspiring
    January 19, 2023

    Hi, Scott (@lsramos),

    you should first have a look at the PDF printer setting that @FrameMaker-dk mentioned in his screenshot.

    That setting ("Use only system fonts, no document fonts") MUST be deactivated as every print-to-(PS)file job (and Save as PDF, too, as it relies on that as well) will fail as long as this is active.

    Regards

    Stephan

    W
    Winfried Reng
    Adobe Expert
    January 19, 2023

    Hi Stephan,

     

    I had not changed this option. It's always activated. Still I create PDFs (via Publish with or without Distiller) or print to PostScript without any issues.

     

    Best regards

     

    Winfried

    M
    mk-will
    Inspiring
    January 19, 2023

    Hi Winfried,

    this is not related to the (new) publish path.

     

    This setting only affects the print-to-file (using the Adobe PDF printer instance) and therefore also the "Save as PDF" command from the File menu.

     

    Regards

    Stephan

    F
    FrameMaker-dk
    Adobe Expert
    January 19, 2023

    When printing to PDF, you may try unchecking this:

    It may help if it is a a font issue, but my guessing is that it is a graphics issue. Tif and eps files have become a problem with FrameMaker and (in my experience) the image headers are at fault. With tif it seems that different cad software produces different tif files and some of these tif exports causes problems. Converting to png fixes this.

    Bjørn Smalbro - FrameMaker.dk
    L
    lsramosAuthor
    New Participant
    January 19, 2023

    This setting is always deactivated before printing now. We have a set of instructions for anyone who intends to publish. Unfortunately, there are many settings like this that have to be reconfigured each time; older versions did not require doing so.

    LinSims
    LinSims
    Brainiac
    January 19, 2023

    You can save most settings to a custom, named joboptions file. Then all you have to do is make sure that's the one selected to have the desired settings in place. (I don't think joboptions will affect whether you use system or document fonts, though, which is a nuisance.)

     

    REALLY  IMPORTANT! Windows has a nasty trick of reassigning your default printer at random intervals. Check for the default printer in Windows settings before you print for release. If Windows did change it to a printer other than Adobe PDF, you'll also need to reselect the joboptions file in the Default Settings field.

     

     

     

    Dave Creamer of IDEAS
    Dave Creamer of IDEAS
    Adobe Expert
    January 19, 2023

    Have you tried the Publish panel? Be sure to edit the settings first.

     

    David Creamer: Community Expert (ACI and ACE 1995-2023)
    L
    lsramosAuthor
    New Participant
    January 19, 2023

    One of many new features that I was unaware of in this new (to me) version. But, a quick perusal of the Publish panel doesn't show me anything relevant to my need. What were you thinking?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices