I have a master project with one topic (intro) and some child projects. Each child project shares terminology with its siblings.
If I build a glossary for each child project (such that I can link the terms to text in the topics), then the master project (which has no glossary of its own) when published has a combined glossary with terms duplicated. For example, the word "Widget" has two entries in the glossary in which the definitions are identical.
If I build a single glossary for the main project and remove the individual glossaries from the child projects, no glossary is generated, and none of the text in the topics have links to the glossary terms.
Is it possible to create a single glossary in the master project and link the terms to text in the child projects? If I could get the glossary to ignore duplicate terms, that would be OK too.
I have worked with merged help for many years and I decided way back to have a single glossary without linking it to the content.
The issues you are hitting are simply the way things are. My own conclusion was that if someone did not understand a term, they would go to the glossary. Bit of a cop out? Yes, but sometimes you have to accept things, at least that was my conclusion.
If you want a more friendly user name that we can use, it can be changed in your settings.
See www.grainge.org for free Authoring and RoboHelp Information
I was afraid of that. Thank you. I might create a Glossary topic at the Master project level until RoboHelp gets an upgrade to accommodate a master glossary.