I'm using RoboHelp 2017 Update 2 for our new product documentation, which will be an HTML5 help with a customized Indigo layout. The product has two different GUIs, one for casual users and one for more experienced users and administrators. The help content between the two GUIs can be switched with dynamic content filters.
The two GUIs are constructed and designed completely differently and I think it would be great to have a dedicated glossary for each GUI.
Now I'm looking for a way to switch the shown glossary depending on which of the content filters is activated. Is this even possible? The glossary files don't seem to have the "Apply conditional tag" context menu entry. Alternatively, can I somehow apply a conditional tag to specific glossary entries (terms and definitions) in the same glossary file?
Otherwise people who can only see the casual GUI will be bogged down by complex terms in the glossary which have nothing to do with what they can see, and advanced GUI users will have the opposite problem.
Thanks for any helpful hints
Copy link to clipboard
I don't think you can achieve what you want as described but there are two solutions that might be acceptable.
The glossary toolbar has a Start Glossary Hotspot Wizard that seeks out all instances of the term used and applies it to the first or all instances of the word in topics, your choice. Use that and then in the skin set Show Glossary to False. This way there is no glossary to be seen but when the user accesses a topic, any words in the glossary will show as expanding text. Users will only see topics according to the filter so will only see the terms aimed at them. That is, assuming the topics and terms match in that way.
The alternative would be to create two glossary topics rather than using RoboHelp's own glossary. They can then be tagged to work with the filters.
See www.grainge.org for free RoboHelp and Authoring information.
Hi Peter, thanks for the quick response and the alternative tipps.
It's too bad the glossary files cannot have filters applied to them. I may open a feature request with Adobe for that. For now your first suggestion (Glossary hotspot) sounds promising .