Skip navigation
ASnyder28
Currently Being Moderated

Cross-References Broken In RoboHelp 10 Output

Jan 18, 2013 7:31 AM

Tags: #robohelp #framemaker #cross-references

We are using FrameMaker 11 to author our documentation. We have some cross-reference links that do not work when the FrameMaker book is imported into RoboHelp. Upon import, the href information is not included in the link in the HTML code. The text looks like a link, however. When the help is generated, the text is not a link.  The following is an example of a non-functioning link:

see <a>Link</a>.</p>

 

Here is an example of a cross-reference that is functioning correctly:

<a href="#XREF_90399_Heading_Text">Link</a>

 

There are no errors in FrameMaker. The cross-reference is updating correctly in FrameMaker. In addition, when a PDF is made form the same book, the cross-reference works in the PDF.

 

Troubleshooting steps I have taken:

  • I have tried going to MIF and back for both the source and target documents.
  • I have recreated the cross-reference and marker.
  • I have tried linking to a heading cross-reference marker, as well as a manually create cross-reference marker.
  • I have renamed the file.
  • I have renamed the marker.
  • I have used different cross-reference formats.
  • I recreated the file by copying all the text to Notepad and pasting the text back into a fresh FrameMaker file.

 

None of the steps I have attempted have corrected the issue for the cross-reference I focused my troubleshooting on. I hope that someone can point me in the right direction to correct this issue.

 
Replies
  • Currently Being Moderated
    Jan 18, 2013 7:35 AM   in reply to ASnyder28

    It's a bug that has to do with the length of the path to your FM docs - shorten up the path & you'll see they start to work in RH

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2013 8:30 AM   in reply to ASnyder28

    It does, but the total path length to a xref is limited to around 25 characters or so - I've never played around enough with it to exactly determine the max length. See this thread for more discussion - http://forums.adobe.com/message/5001958#5001958

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2013 9:50 AM   in reply to ASnyder28

    And you updated the book in FM first in the new location before importing? I'd try something really short off the c:\ root directly - your desktop (depending on the version of Windows) is still a long path you know.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 18, 2013 10:43 AM   in reply to ASnyder28

    are some working & others not?

     

    There were reports of a bug that had to do with xrefs that pointed back to earlier positions within the file - references like "See xxx on page yyy" were supposed by the Conversion Settings to end up as "See xxx" would get a mix of ones that were correct & ones that weren't.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 2:02 PM   in reply to ASnyder28

    @Peter - when you get a chance, can you move this one into the FM Integration forum?

     

    @ASnyder28 - The RH project should have already been on C:\ (best practices advises c:\projects\{project_name}\ as a structure). What's the path length to the remaining busted link? There seems to be an invisible limit of under 35 characters (no spaces either) to these things. You may have to relink the xref in FM first before sucking it into a new project.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 6:49 AM   in reply to ASnyder28

    Oh I'd say it's a bug all right - the more people complain about it, the better chance it has of being addressed. If you have support, contact Adobe Support and hassle them. If not, file a bug report.

     

    I ran across it in an earlier version of TCS but it took me some time to run down the cause & even then, I haven't identified the invisible limit exactly - I know it's around 35 characters (that's total path and .fm file name length), but it could be less.

     

    Just like you, I've got lots of folder structure to my content - I use the "master book of books" concept to suck in around 60 sub-books into RH (by import; linking in earlier versions would crash). I had always noticed that some of the xrefs that I was sure were present & working in FM were busted in the resulting RH WebHelp output, but didn't have enough time to chase it down. It was when I was looking closely at a page of "what's new" notes that I was writing that I saw some xrefs work & others not all on the same page - that got me digging into the HTML code where I saw the malformed href= links. Tracing it back led me to believe it had to do with some really long paths that I was sort of stuck with until I could move the entire load of them into a shorter path name. Once I did that, they all seemed to clean up.

     

    Another poster with a thread almost identical to this one has sent me their files to play with because shortening the path length didn't fix all the busted xrefs. I still have to play with them to see what's going on.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 31, 2013 11:24 AM   in reply to ASnyder28

    Hmm, that's interesting - I don't use text insets in my projects, so I hadn't run into that, but it's good to know.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 11, 2013 6:58 AM   in reply to ASnyder28

    Hi,

    Try running the RoboHelp update available here:

    http://www.adobe.com/support/robohelp/downloads.html

    I had issues with cross-references not converting properly in TCS4, and this update fixed the problems.

    Alexandra

     
    |
    Mark as:
  • Currently Being Moderated
    May 22, 2013 7:47 PM   in reply to zandwich

    For what its worth, I came across this thread after running into this issue as well. I'm glad I read to the bottom and found @ASnyder28's post about the text insets. I copied my file, converted all of the text insets, and voila! Correctly converted cross references.

     

    I don't really like this solution, but for a help project that needs to be delivered tomorrow, it works.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 3, 2013 6:41 PM   in reply to ASnyder28

    To add to the joy of those that got their xrefs fixed with this patch:

     

    I just discovered 2 things:

    1. My Rh wasn't patched up to 10.0.1
    2. Solving Thing #1 solved an issue with spot cross-references. I have now regained control of my spot xrefs.

    Thx to the Rh team for putting out the patch!

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 23, 2013 6:33 AM   in reply to mattrsullivan

    We are working with TCS 3.5 and RH 9 and FM 10.

    The problem is the same.

    We have two projects with missing Cross references in Robohelp after importing from Framemaker.

    The cross references worked fine until I started to work with text insets.

     

    We want to use text insets intensively in the future. As a modular system. This is very important for us.

    Crossreferences are essential for online help systems, two. What to do?

     

    What we need is an update for Robohelp 9 that fixes this problem.

     

    Hope, there is someone with good news

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 23, 2013 6:40 AM   in reply to A-Bel

    Don’t hold your breath – you need to upgrade to TCS 4 because with a new version coming 2014, they’re not doing much fixing in any but the prior release.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 4, 2013 3:20 AM   in reply to Jeff_Coatsworth

    Thanks for your reply!

     

    Well, we bought the TCS in November 2012.

    For our small company this was a big step foward, but also high expenses.

     

    An update is my worst case: 1.300 € for each licence  for one bug fix.

     

    So, there is no angel of mercy with a patch for RH 9. Is there any way to address

    my request to Adobe?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 4, 2013 8:20 AM   in reply to ASnyder28

    Thank you for your support.

    The bug report for RH is done. But I can't refer to it. Perhaps Adobe is going to send me a link or a reference number...

     

    The RH patch 10.0.1  isn´t the fix?  That's what I understand from MattRSullivans response.

     

    I remain a bit puzzled

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 4, 2013 12:22 PM   in reply to A-Bel

    Actually, the patch resolved my issues.

     

    It sounds as if there's an issue with xrefs within text insets, which doesn't apply to me. However, I tend to design around such limitations...living to fight another day!

     

    Lobby for the increased functionality at adobe.com/go/wish (already done, I think) and then hurry up and wait to see if it makes it into the next version!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 5, 2013 12:35 AM   in reply to mattrsullivan

    Seems to be not that simple. We will test it with the TCS 4 trial version. As we have a 2nd cross reference problem in another project without text insets, but with the same behaviour (all external cross refs unresolved after import/ link) there might be a 50% success.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points