Not a question. Just sharing the knowledge I gained from converting our RoboHelp HTML topic-based glossary to RoboHelp HTML's .GLO glossary.
For years we've provided a glossary via a single topic; terms and definitions were presented in 2-column tables - one table for each letter, A-Z, top to bottom. Jump links for each letter at the top of the topic. For various reasons, I've been looking at the .GLO function (I really like the hotspot wizard, but I'm still not sure if it'll create any unintended formatting consequences with our content (thousands of topics)). We have a couple hundred terms and manually copying/pasting them in RoboHelp HTML is NOT something we want to do so I decided to see if I could automate most of the process (particularly since there's a single .GLO file and the guts of the terms/definitions is basic HTML).
What you'll need:
These are the basic steps. It took a little trial and error so these may not be exact, but there should be enough here.
<glossentry> | <glossterm> | TERM | </glossterm> | <glossdef> | TERM DEFINITION | </glossdef> | </glossentry>
Nice of you to provide the steps needed in the event someone needs them.
I'm curious, however, about what led you to the decision to abandon your topic glossary and opt instead for the RoboHelp supplied glossary?
When I facilitate a RoboHelp class, I usually mention that one also has the option of a Topic glossary as well as describing the limitations of the RoboHelp glossary. For example, using just the GLO file, you aren't able to insert images and provide links that point to additional content.
Hi Rick. We haven't committed to switching, but we're evaluating it. We have several hundred terms, and manually copying/pasting those from a topic to the GLO pod would probably be sufficient to nix such a move. So this was a proof-of-concept exercise to see if/to what extent I could automate the switch. As to why we're considering the switch, here are several factors:
Obviously, many things to consider! We haven't made a decision, so if you have any additional thoughts on one vs. the other, please share!
<?xml version="1.0" encoding="utf-8"?>
Where can I find out what the "illegal" characters are? Also, I want to include <href> </href> links in my glossary. Some of those include illegal characters such as a ? or @. Will that prevent my glossary from being usable in RH2017?
Works like a charm
Thanks for that