Skip to main content
Known Participant
December 29, 2017
Answered

Robohelp 2015, HTML5 Responsive Help, Parent and child projects, hyperlinks

  • December 29, 2017
  • 1 reply
  • 479 views

Hi

I am planning to publish help online as HTML5 Responsive help rather than locally installed CHM files.

I have published my child projects into the MergedProjects folder OK for HTML5 Responsive help. When I open the index.htm file of my parent project the merged projects are displayed correctly in the TOC. The Search also works fine across parent and child projects.

However, hyperlinks are not preserved  if they include the CHM file in the hyperlink. As a rule, I include the CHM file so that the link between CHMs will always work.

For example, links will not be preserved in the HTML5 Responsive help (no underline, no hyperlink).

Parent.chm::/GettingStarted/Notes.htm

Child1.chm::/MoreNotes.htm

Child2.chm::/EverMoreNotes.htm

But this link is preserved (underlined and hyperlinked).

/GettingStarted/Notes.htm

I need the links between CHMS, and within CHMS, to be preserved in HTML5 Responsive help. Is there an answer to this?

Thanks!

This topic has been closed for replies.
Correct answer Peter Grainge

The format of links for CHMs and WebHelp/Responsive is different and the only solution is to create both and apply build tags. Then you use build expressions to get the link you want for that output.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

1 reply

Peter Grainge
Community Expert
Peter GraingeCommunity ExpertCorrect answer
Community Expert
December 29, 2017

The format of links for CHMs and WebHelp/Responsive is different and the only solution is to create both and apply build tags. Then you use build expressions to get the link you want for that output.


See www.grainge.org for RoboHelp and Authoring information

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Known Participant
January 2, 2018

Okay, thanks Peter. I was afraid that would be the answer.