Login using the username and password you created for AcrobatUsers.com.
Note: This is not the same as your Adobe ID.
Benefits of Free Membership:
Find out what AcrobatUsers.com is all about
You don't have to be a member to look at any content on the site. Increase your expertise with our helpful tutorials, videos, forums, and sample PDFs.
Like what you see? Take the next step and become a member. Register now to get discounts, attend eSeminars, ask questions and more.
Get the most out of your membership. Post in the forums, create your profile, submit to the gallery, attend a user group meeting. Log In now.
Pages: 1
ANSWERED
I am working on a document in FrameMaker 7.2 that we are trying to break into two different documents while retaining the cross-reference linking between the two book files. When I print to PDF (PS file to Distiller), the links between the two documents remain intact, but as soon as I upload them to our SharePoint, which publishes to the Web, the cross-reference links between the two documents work, but will take the user only to the first page in the file, whereas before they were taking the user directly to the specific point in the PDF. I know that FrameMaker inserts a prefix before destination tags, which is, ultimately what the links become, but I'm not sure how to get rid of it or why it's affected only after the document is published to the Web.
Any help at all would be appreciated.
Thanks!
My Product Information:
Acrobat Pro 9 / Windows
Offline
ACCEPTED ANSWER
Hi,
A FM cross-reference link, in PDF, is of a form like this:
<some path>\filename.pdfDestination name:<unique named destination alpha-numeric>.paragraph tag.<unique alpha-numeric><cross-reference text>
I did a trial using two FM Books, each containing a single FM file.
Book 1's FM file 1 had a cross-reference link to a marker set to a specific paragraph tag & its associated, short, text string.
Basically, modeling what is done with more detailed Books/files inter linkded with FM cross-references.
With the two Books open, an output PDF for each was processed.
Put both PDFs into "web space" at a domain I maintain.
Viewed PDF 1 (from Book 1) that contained the link to PDF 2.
Used MSIE 8 and Acrobat 8 3D for this (wouldn't expect difference using IE 6 or 7 & Adobe Reader/Acrobat 7 (fully updated) or 9).
The link brought me to the specifide destination in PDF 2.
So in "true" web space there ought to be no problem.
From this, I suspect it is a high probability that the SharePoint out to "web" process or the "web" associated
with the SharePoint server is truncating what it processed/serves to the browser you are using.
It (the SharePoint environment) is only passing the link up to the file extension.
This is consistent with observations over time that MS and Adobe use common characters to do different things.
i.e., the # character, used in Word with Word bookmarks from one file to another is used for another purpose by Acrobat (open parameters use #).
As there is not an unlimited supply of ANSI characters this kinda makes sense.
Be well...
Last edited by daka630 (2010-01-23 20:17:28)
Offline
Thanks for the response. Do you have any suggestions for how to make it work? Do you think the problem could be caused by the prefix FM puts on the link? On the FM MicroType Web site, there is mention of an option "Delete 'mX.newlink.' prefix of newlink markers starting with:" function in the Links/General tab. I've thusfar been unable to find this mysterious function, but would like to try it to see if removing this prefix would remove the problem. Have you heard of this function before?
Offline
Pages: 1
Copyright © 2009 Adobe Systems Incorporated. All rights reserved.
