Cross-file links in PDFs authored in FrameMaker 8.0 use Unicode-encoded 
file paths and file names, which are only supported in Windows 
Acrobat/Reader 8.x (MacOS Acrobat/Reader 7.x or later; I don't have info 
for Unix Reader versions).

As a result, cross-file links are not functional when the PDF is displayed 
in earlier Acrobat/Reader versions, even though the target PDFs files are 
present in the target location.

When clicking the cross-file links, the following message is displayed: 
"There was an error opening this document. The path does not exist".
Some FM8->PDFs with cross-file links trigger the following message upon 
opening in Acrobat/Reader versions earlier than 8: "This file appears to 
use a new format... Adobe recommends that you upgrade to the latest version 
of our Acrobat products...".
(note: Acrobat compatibility setting used in Distiller options does not 
affect this behavior).

System requirements for Reader 8.0/Windows are at:
http://www.adobe.com/products/acrobat/acrrsystemreqs.html#80win

End users who do not use a Reader version which supports Unicode-encoded 
file paths/names will experience the error when clicking cross-file links 
in PDFs authored with FM8.0, even though the links are valid on the PDF 
producer's system.

This could potentially be an issue for PDF producers with end users in 
environments where the latest Reader version available is relatively old -- 
these should test Unicode-encoded file paths/names in all Reader versions 
to be supported.

[ A related issue: at least with FM7.x, internal links may sometimes be 
written as external links when using "Save as PDF" - see 
http://www.microtype.com/homeHmmm.html ].


Shlomo Perets

MicroType, http://www.microtype.com
Training, consulting & add-ons: FrameMaker, Structured FM and Acrobat



Reply via email to