Skip to main content
Participant
November 5, 2021
Question

FrameMaker Publish Responsive HTML5 - Multiple Books With Broken Xrefs Between Books

  • November 5, 2021
  • 3 replies
  • 253 views

FrameMaker 16.0.3.979; Windows 10 Enterprise 1909 (18363.1854)

 

When I publish multiple books as PDFs, the hyperlinks from one book to another work as they always have. In other words, cross-references within one book that link to a heading in another book function as expected.

 

When I publish these same books as Responsive HTML5, these cross-references from one book to another do not work. The cross-references from one place to another within the same book still work, though.

 

Is there anything that I could be missing in the Publish settings?

This topic has been closed for replies.

3 replies

Legend
November 10, 2021

Since these are all text files, a simple script could probably do a search and replace through the files, looking for the wrong folder and replacing it with the correct folder. I know this is not a solution directly from FrameMaker, but it seems like the simplest solution to me. If you wanted to launch the operation within FM, you could use ExtendScript. Or you could do it externally with any scripting or programming language, such as Python. In all cases, it should be a very short and basic script, I suspect easier to implement than to modify your FM workflow.

Participant
November 10, 2021

Thank you, Russ! I'll take this idea up with my team. We might have someone who knows Frame scripting already, or who can whip up a Python script faster than I can. Thanks again!

Jeff_Coatsworth
Community Expert
Community Expert
November 9, 2021

I think the only way that would work is if you used the "book of books" model and published the one master book containing all the child books. Then the cross-book links would resolve. 

Participant
November 9, 2021

I'm afraid that might be the only way; thank you.I submitted a support case because the book-of-books model comes with its own set of hurdles in our situation.

Thank you!

Participant
November 5, 2021

Some more details to add:

The broken reference link points to the wrong folder (that is, the current book's HTML5 output folder), but is looking for the correct file name, which resides in the other book's HTML5 output folder.

I publish HTML5 one book at a time (no other option to publish multiple book files at once) and the FrameMaker book files are at the same directory level. This all works when generating PDFs.