Skip to main content
Inspiring
February 25, 2010
Question

Fix SaveAs PDF or rip it out....

  • February 25, 2010
  • 3 replies
  • 3810 views

To amplify another post (http://forums.adobe.com/thread/560103?tstart=0), the SaveAs PDF code is FrameMaker is so unreliable and unpredictable that it shouldn't be inflicted on users...It's even worse that this menu item hasn't worked well for several releases.

It should be embarassing to Adobe that the company can't support this.

Either disable the code so that people print to the Acrobat printer instance, or come up with reliable code...

This topic has been closed for replies.

3 replies

Inspiring
May 7, 2010

Please don't get rid of 'save to PDF'!  It's my entire business.  Everything in the world I sell is a pdf generated from FM.

But it would be nice if it were more predictable.  One day last month it stopped working for me, and I spent an entire day on the phone with your tech support team.  At the end of the day, their answer was, "we don't know why it doesn't work, and don't know how to fix it."  Unsettling.

Arnis Gubins
Inspiring
May 7, 2010

Allen,

One can always use the AdobePDF printer instance and create PDFs from FM. FYI, this is the same mechanism that SaveAsPDF uses behind the scenes, albeit without all of the jumping through hoops and lousy integration. This is what the main complaint is about - it's not always reliable and is not properly designed for print(press) production PDFs.

mandrill22
Inspiring
May 3, 2010

I am using 8.0p277 and have given up on the PDF feature working properly. My company upgraded Acrobat Pro from 7 to 8; after that, the Save as PDF never worked and FrameMaker kept telling me that the feature was either not installed or I needed to upgrade it. I downgraded to 7 to get it to  work partially and intermittently. Now sometimes it makes a PDF and other times it creates the *.tps postscript file and stops there--I can create a PDF by coaxing the *.tps to move on by dropping it in Distiller.

I used the trial version of 9.0 and it seemed to work OK there.

Participating Frequently
May 7, 2010

If I remember me correctly, Acrobat 7 to 8 changed the PDF Printer. 7 with AcroDist to 8 with AdobePDF. Please check this little requirements.

- Georg

mandrill22
Inspiring
May 7, 2010

Hi Arnis.

Thanks for the prompt response.

Wow. I guess the Acrobat and FrameMaker development teams eat in different

cafeterias.

Question: does this get easier with FM9? I'm using 8 now.

Jack


Allen,

I suspect the FrameMaker team are mostly vegetarians while the Acrobat team is mainly made up of carnivores. This may be the real reason behind the "Save As PDF" (sap?) menu item working like a button that needs to be sprayed with contact cleaner.

Arnis (Post #11) is right about this being just a "convenient" automation of doing a bit manual work. I don't think the original message post was suggesting losing the functionality of creating PDFs--it was just an expression of angst at having paying paid for a button that does not work as well as it used to.

April 22, 2010

Art, I don't seem to have a problem when saving to PDF.  I'm a new user of FM and am using FM 9 as part of the Technical Communications Suite (Acrobat Professional is part of the suite).  In addition, I use a plugin to author iSpec2200 compliant documents.  Is it possible I'm not having problems because of the extra tools I'm using, or is the problem you described an intermittant problem I just haven't seen yet?  It would seem if it's a problem with FM code I would be having problems regardless of the additional tools.

Eric G.