.chm TOC using variables - print SSL does not recognize anything after the variable

[eeddings]

Here's an interesting thing I stumbled upon today.  I think this may be a bug in RH 10.

I create .chm TOCs using variables.  For TOC page entries, any content before the variable in the TOC entry converts to the print TOC without problem.  But, any content after the variable is ignored.  This is only an issue with pages in the TOC.  Books are fine.

For example:

TOC Book:

"Clinic - {variable} {variable}"

This translates fine to the print TOC in a printed documentation SSL.

TOC Page:

"Clinic - {variable} {variable}"

Aside from the link in the TOC page, the code for the TOC book and the TOC page looks identical.  But, for some reason, anything after the *first* variable in the TOC page is ignored in the print TOC for the printed documentation SSL.  It doesn't matter if it is another variable or straight text.

In the picture above, both the "Clinic - Participant List screen" TOC book and TOC page on the left contain two variables:

"Clinic - {variable} {variable}"

On the right "Clinic - Participant List" page, the "screen" variable is ignored and removed on the TOC page only when the chapter layout is created for the print SSL.  RH will remove anything after the first variable in the TOC page, regardless of whether it is a variable or straight text.  RH does not remove antything from a TOC book when the chapter layour is created for print (visible in the image above).

Message was edited by: eeddings -- added image to show the bug visually.

[Peter Grainge · Accepted solution]

When you generate printed documentation any book titles will go into the printed document.

Pages in the TOC of the document are based not on what is in the TOC shown above but on the topic heading.

Add the variable there and it works.

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

[eeddings]

Thanks for the reply, Peter.  Yes, that's exactly what I'm seeing as well.

[Peter Grainge]

To be clear, I don't see that as a bug, rather than the result of how the document is produced.

---

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge