Glossary tab not appearing in RoboHelp9

Forum|Forum|14 years ago
February 21, 2012
1 reply
1420 views

Yes, I have read the other posts on this topic, but am still having the problem.

I have a RoboHelp project, with a glossary, that I've published to several layouts. The glossary appears in the web layouts (but, for some reason does not work in Chrome), AIR, and even in the printed documentation. In MS HTML Help, however, I don't even get a glossary tab. I have RoboHelp 9 installed, and I've manually re-registered HHActiveX.dll. In the MS HTML Help layout properties, I've selected both <Default Glossary>, and the project name (the only other option provided). Either way - no glossary.

I've triex everything I've read, but still don't even get the tab. What am I missing?

Specs:

RoboHelp 9

Windows XP Pro, 32-bit

HTML

This topic has been closed for replies.

Correct answer Peter Grainge

Ignore the highlighting in this screenshot. This is where you enable to glossary tab that Rick is referring to.

MS HTML help must be the default layout when you create the window.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Captiv8r

Legend

Welcome to our community

Did you try creating a new Window definition and specifying that it has the Glossary enabled?

Cheers... Rick

Helpful and Handy Links

RoboHelp Wish Form/Bug Reporting Form

Begin learning RoboHelp HTML 7, 8 or 9 within the day!

Adobe Certified RoboHelp HTML Training

SorcerStone Blog

RoboHelp eBooks

Peter Grainge

Correct answer

Community Expert

Ignore the highlighting in this screenshot. This is where you enable to glossary tab that Rick is referring to.

MS HTML help must be the default layout when you create the window.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

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

RoboColum_n_

Legend

Colum: Thanks for the pointer. Yes, I was aware of the different layouts, and use the SSL pod frequently. I do understand why different windows are needed for different layouts. Which bring me to...

Peter: I agree that the "window created is always should be the window for whatever is the default layout at the time", but I have never had WebHelp Pro set as default (or even had it selected), so don't know why RH created that type of window when I clicked on "New Window". Which brings me to...

Colum and Peter: The first comment in Colum's referenced column was yours, Peter, where you suggested that the user be given the option to select the window type, when creating a new window! That would have solev my problem, and, in general, would be extremely helpful. As you posted that comment two years ago, I'm not holding out much hope that Adobe will listen.

I'm afraid you'd be right to not hold out much hope for Peter's excellent enhancement request. The more people that request it though could sway Adobe to implementing it in a future release, so please do take the time to do so. As for why the windows are created in a certain way, could someone else have been using the project? A window's default settings are taken according to the default SSL........period. I you didn't set the default SSL to WebHelp Pro, maybe someone else did?