How did you create your glossary?

[alaltenburg]

Hello,

I am looking for different ideas on how to make the glossary. How did you create your glossary? Did you use the proxy or a workaround?

Thanks!
Andrea

[Nita Beck]

All depends!

For one of my projects, I've used Flare's glossary feature. I added terms to the glossary file. It's nice that Flare manages the alpha order for me.

For another of my projects, I created individual .htm files for the terms, some of which have extended definitions with illustrations. On the TOC, I have a Glossary book linked to a glossary.htm file. In that file, I don't use a glossary proxy (since I'm not using Flare's glossary feature), but I do use a mini-TOC proxy. Then under the Glossary book in the TOC, I've got entries for all the terms. Yeah, I have to alphabetize them myself, but, hey, that's not so hard! (Actually, the project I speak of is a global project that product-specific projects import from. In the global project, I've conditionalized the term files for the different products I support, and in the product-specific projects, I've set up import rules that pull in only those term files that are relevant.

Regardless of how I've created the glossary, I generally don't like glossary links in topics. I think they are distracting. I figure that, with the Glossary always a book at the bottom of a TOC, the user can look up a glossary term as needed. That said, I do occasionally include a popup link to a glossary term. I never have Flare create automatic glossary links for me (and if I did, I don't think it would support the second method I've described above).

Hope this gives you some ideas.

[alaltenburg]

Nita,
Thank you for your response to my post. It seems the glossary proxy is not very practical for most of the glossaries needed in this company. I am probably going to work on making each term it's own .htm file. I was just hoping the proxy had more flexibility than it does.

Thanks!
Andrea

[LTinker68]

Make sure you submit a feature request at http://www.madcapsoftware.com/bugs/submit.aspx outlining the flexibility you'd like to have in the glossary.