Known Participant

Question

Select cross-refs are not linking in ePub output

Forum|Forum|11 years ago
October 1, 2014
1 reply
840 views

We publish very large documents and are slowly transitioning them into ePubs. They contain tons of cross references - most of which work fine. However, there appears to be one type of cross reference that does not work (i.e. link) in the ePub output. It looks like it should work based on the publish settings, and it turns blue in the ePub. It just doesn't link. Not sure how to fix it. Would it help to attach an ePub file? Thanks in advance for the help!

This topic has been closed for replies.

Jeff_Coatsworth

Community Expert

Can’t do attachments on the forums – but I suspect that you may be running into a hidden limit that exists that seems to wreck some cross reference links when going from FM to some output formats. Try creating WebHelp and see if the same links fail – if so, it’s probably because the total length of the FM path and file name can’t be more than about 35 characters or so – shorter is better. If you’ve got a long path and file name, you’ll have to shorten it up. Try copying the project to your root c:\ drive and test it from there.

S

SER617Author

Known Participant

Thanks Jeff. Forgive my ignorance, but how would you shorten the path

and file name for a cross-reference? Is there a way to view the entire

path name being used?

>>> Jeff_Coatsworth <forums_noreply@adobe.com> 10/1/2014 2:07 PM >>>

Select cross-refs are not linking in ePub output created by

Jeff_Coatsworth

( https://forums.adobe.com/people/Jeff_Coatsworth) in FrameMaker -

View the full discussion

( https://forums.adobe.com/message/6781728#6781728)

Can’t do attachments on the forums – but I suspect that you may be

running into a hidden limit that exists that seems to wreck some cross

reference links when going from FM to some output formats. Try creating

WebHelp and see if the same links fail – if so, it’s probably because

the total length of the FM path and file name can’t be more than about

35 characters or so – shorter is better. If you’ve got a long path and

file name, you’ll have to shorten it up. Try copying the project to your

root c:\ drive and test it from there.

Please note that the Adobe Forums do not accept email attachments. If

you want to embed a screen image in your message please visit the thread

in the forum to embed the image at

https://forums.adobe.com/message/6781728#6781728

Replies to this message go to everyone subscribed to this thread, not

directly to the person who posted the message. To post a reply, either

reply to this email or visit the message page:

To unsubscribe from this thread, please visit the message page at

. In the Actions box

on the right, click the Stop Email Notifications link.

Start a new discussion in FrameMaker by email

(

mailto:discussions-community-framemaker@adobe-v7.hosted.jivesoftware.com)

or at Adobe Community

(

https://forums.adobe.com/choose-container.jspa?contentType=1&containerType=14&container=3389)

For more information about maintaining your forum email notifications

please go to http://forums.adobe.com/thread/416458?tstart=0.

Jeff_Coatsworth

Community Expert

Start by testing shortening the path – preserving whatever structure you’ve got for your books and documents, and copying it to a c:\projects\ folder. I’ll use an example that I had – my whole FM project used to be here (because I didn’t know any better): P:\Departments\QA Department\Jonas Documentation Conversion Project\doc_projects\content\ with a pile of sub-folders that corresponded to each module in the product. So for example, one doc could be in P:\Departments\QA Department\Jonas Documentation Conversion Project\doc_projects\content\Club Management\Club Gift Certificates & Rain Checks reference.fm making a link to P:\Departments\QA Department\Jonas Documentation Conversion Project\doc_projects\content\Banquet & Catering\Banquet & Catering Srv Chrg Labor to Payroll overview.fm – clearly a ridiculous length. But by shortening the path just to P:\Departments\QA Department\doc_projects\content\ and keeping the same subfolder structure, I was able to preserve all my xrefs and keep them intact when output to WebHelp.

I could have gone in and renamed the FM docs themselves (doing them one by one within FM to prevent broken xrefs) also, but I found just moving the whole folder structure worked too. This will only work if all your xrefs are to other docs/images within your folders; any links that cross the root folder will end up busted when the project is moved.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded