Iam unable to get merged help to work in Multiscreen HTML5 Help

Report · Jan 20, 2014

I have just started to try out the RoboHelp 10 Multiscreen HTML5 format and have found a problem with merged projects.

I carry out the usual procedure for merged projects by adding each child project to the TOC of the parent project then generate and publish each one.

Upon viewing the published help system, the parent project is correct with the TOC showing the child topics.

However, upon clicking on a child topic in the TOC the child topic will open but shows as a standalone project, i.e. the TOC/Index etc no longer shows the whole merged project.

I am using the same screen layout for all projects and have tried using various other default RoboHelp screen layouts, all without success.

I can publish the exact same project using WebHelp and everything works perfectly.

Is there an extra step somewhere for Multiscreen HTML5?

Chris

Report · Jan 21, 2014

Merged help is not viable with HTML5 in Rh10 or 11. I am nagging Adobe to make it work in Rh12 but clearly that is a long way off.

Please follow this link.

http://www.Adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · Jan 21, 2014

Such harsh words Peter

Merged help works quite different in HTML5 than WebHelp.

I described the process of merging HTML5 on:

https://www.wvanweelden.eu/blog/2012/12/27/merging-multiscreen-html5-help

Kind regards,

Willam

Report · Jan 21, 2014

I had issues with that but will give it another go as I cannot recall what they were now.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · Jan 21, 2014

Something about the WebHelp workflow being not compatible with HTML5 if

I'm not mistaken. The links between projects are completely different in

merged Multiscreen HTML5. I believe that was the main issue.

Kind regards,

Willam

Report · Jan 21, 2014

Indeed young man with a better memory!

I think it was the case that all those links would need reworking in an existing project and multiple outputs you would need build tags. Throw in printed documentation and it would be a nightmare.

So, possible with a new project and your workflow and possible with existing projects but you have to accept a lot of reworking if there are lots of cross project links.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · Jan 21, 2014

Thanks Peter and William. At this stage I am not worried about cross project links, and by this I am assuming you mean manual links placed in the topic of one project to link to a topic in another project.

At this time I am just attempting to build a Merged project so that the TOC, Index etc work correctly. To do this I have followed Williams instructions, which to me appear to be the same as any WebHelp project;

"Merging child projects into the parent project

You merge the child projects through the master projects’ TOC. Go to the TOC and click the button New Merged Project. Now select the XPJ of the child project you want to merge.

You will now find the name of the child project in the master projects’ TOC. And that is all you need to do. All further merging is automatic. Table of contents, context sensitivity, no further manual action required."

However, this does not appear to work - at least for me

I think Peter you are right, it simply doesn't work correctly. I will complete a report to Adobe.

Thanks guys.

Chris

Report · Jan 25, 2014

Very strange. Can you open the developer console in the browser (by

pressing F12)? Then load up the help. Do you get any errors on the

console tab?

Kind regards,

Willam

Report · Jan 27, 2014

Hi William,

Pressing F12 and selecting the Console tab on my IE9 browser reveals the following information message:

"HTML 1113: Document mode restart from IE7 Standards to IE9 Standard".

I don't know what that means?

Anyway, Adobe have come back to me asking for a copy of some project files. I will pass these on to them and let you know if I hear anything further.

Thnaks for your interest.

Cheers,

Chris