Deja Vu?? Was: Using SAVE AS PDF in FrameMaker 6.0

[Shlomo Perets]

Rebecca Officer wrote:

>According to Shlomo Perets' website
>(http://www.microtype.com/FM_bugs.html) people have reported issues
>with FM7.x and Save As PDF when using Win98, or tagged PDF, or custom
>page sizes, or Acrobat 6.x.
>
>We seem to be fine with it, but we're not using any of the above. ;-)

Some additional issues related to "Save as PDF" are listed in "FrameMaker 
Annoyances" -- under different FM releases, such as:

* The Save as PDF function does not report switching of drivers – output 
may not match current FrameMaker layout (line breaks, page breaks) or 
reflect missing fonts. (unless "Adobe PDF" is the default printer driver)

* The combination of "Save as PDF" and Tagged PDF may result in some 
anomalies, such as missing text in shaded table cells.

Other issues have been mentioned in the mailing list, see below.

However way the PDF is produced, it should be thoroughly tested.

Shlomo


>Date: Sun, 27 Nov 2005 07:14:55 +0200
>To: Martin Polley <martin_keren at shaar-hagolan.co.il>
>From: Shlomo Perets <shlomo2 at microtype.com>
>Subject: Re: Rename PDF, xrefs stop working (more)
>Cc: Framers at FrameUsers.com, frame2acrobat at yahoogroups.com, 
>Kathy.Bowman at saabsystems.com.au, james.brandal at c2i.net
>
>Martin,
>
>You wrote:
>
>>With some of the PDFs that I create, if I rename them, the
>>cross-references stop working, giving this error:
>>
>>     The specified file <old file name> does not exist.
>>
>>Does anyone have any idea why this is happening? Is there a workaround?
>>(Other than "don't rename the file"...)
>
>As I mentioned earlier, some of the older FrameMaker 5.x versions specify 
>internal links with a file name target, in which case renaming the PDF 
>causes bad links (even when the PDF is stand-alone, with no links pointing 
>to it from other PDFs).
>
>Upon further examination, I was able to reproduce the creation of PDF 
>links which use a filename even though the link is internal in FrameMaker 
>7.0, 7.1 and 7.2, but only when "Save as PDF" was used.  In the same 
>tests, the problem was not encountered even once when printing books to a 
>.ps file and then distilling to PDF.
>
>Given this FrameMaker bug, we may have yet another reason to stick to the 
>original PDF file names, yet another reason to print to .ps rather than 
>Save as PDF, and yet another reason to test PDF links carefully...
>
>
>Shlomo Perets
>
>MicroType, http://www.microtype.com * ToolbarPlus Express for FrameMaker
>FrameMaker/Acrobat training & consulting * FrameMaker-to-Acrobat 
>TimeSavers/Assistants
>Template Design, Single Sourcing, FM-to-PDF & Technical Indexing seminars