How to have Glossary in Word output

[Cecily]

My project is normally output as html help.

It includes a glossary that a colleague would like to use in a Word document, but it isn't included in the Word output and I can't just copy and paste as it from Flare as it comes through with all the xml tags.

My workaround was to open the html output, open the glossary, expand each entry, copy and paste from there into Word and then format it in Word.

That worked, but surely there's a quicker and easier solution?

[KevinDAmery]

You can add a glossary topic. What you'll need to do is create a new page layout for glossaries and add a glossary proxy to it. Then add the topic to your word output TOC and build the output.

(What I usually do is set the glossary topic up as print-only using conditions because I don't want it in my CHM files.)

[LTinker68]

Actually, the glossary proxy won't work in online outputs, at least not yet. So if you don't apply the print-only condition, then you'll get the glossary topic in the online help but the contents will be blank except for the title. Likewise with the index proxy.

[KevinDAmery]

True, but I don't want a blank topic either

[Cecily]

Thanks for the suggestions. However, they don't sound much quicker than the way I did it (especially as it's unlikely to be a frequent request).

[scott]

Hi Cecily,
The glossary proxy should appear in your HTML Help, and you can force the definitions to be displayed using CSS. The only downside is that the user won't be able to close them. I think that's OK for your goals, though.

The glossary definitions use the div.GlossaryPageDefinition style. The display property is set using inline formatting to 'none.' We need to set it to 'block.' Here's how:

* Open your stylesheet in the internal text editor (right-click the stylesheet in the Content Explorer and select Open with > Internal Text Editor).
* Find div.GlossaryPageDefinition. If it's not there, you can add it.
* Set up the style as follows:

div.GlossaryPageDefinition
{
display: block !important;
}

The trick is the !important value. That overrides the inline formatting that makes your definitions hidden. !important is also what prevents it from being closed when the user clicks the glossary link.

hope this helps,
.scott