Glossary output

Having trouble installing <oXygen/>? Got a bug to report? Post it all here.
Stacey
Posts: 16
Joined: Tue Mar 14, 2017 12:36 am

Glossary output

Post by Stacey » Tue May 11, 2021 4:10 pm

I've tried creating a Glossary map and a glossgroup topic. We typically create PDF output (we do both PDF and WebHelp, but this is an issue in PDF, not WebHelp [well, it happens there too, but it doesn't matter]).

Each <glossentry> is being treated as its own topic and being placed on its own page. I've tried using the chunk option on the .ditamap (a submap in the document map) and on the glossref topic. Neither seems to output the content as "one" page. Am I using the wrong attribute value or applying it in the wrong place?

We want topics in the main document to be on separate pages, and the glossary should be part of that document, but in the glossary, terms should be on the same page(s) as much as space allows.

julien_lacour
Posts: 174
Joined: Wed Oct 16, 2019 3:47 pm

Re: Glossary output

Post by julien_lacour » Wed May 12, 2021 9:41 am

Hello,

I tested on Oxygen 23.1 and cannot reproduce the problem: all my glossgroup glossentries are displayed on the same page.
Could you indicate which version of Oxygen you are currently using?
Also, is it possible for you to test using the predefined DITA Map PDF - based on HTML5 & CSS transformation? Do you obtain the same result?

Regards,
Julien

Stacey
Posts: 16
Joined: Tue Mar 14, 2017 12:36 am

Re: Glossary output

Post by Stacey » Fri May 28, 2021 3:10 pm

Hi Julien:

I forgot we were using customized files.

With the DITA Map PDF - based on HTML5 & CSS transformation I do get them all on one page, but it adds "Chapter 1." at the beginning.

I tried omitting a parent "glossary" topic, and it gave each term its own chapter (571 chapters, ha!).

The font/headers and footers/topic breaks/etc. we usually include are obviously missing as well.

How would I recreate that/start from scratch on creating that?

And is there a way to include a glossary as back matter/with separate breaks than for the rest of the book? I think that's what the problem is - our customization includes page breaks to a TOC level 4, but in the glossary section you really only want a page break for a TOC level 1.
image.png
image.png (13.62 KiB) Viewed 131 times

julien_lacour
Posts: 174
Joined: Wed Oct 16, 2019 3:47 pm

Re: Glossary output

Post by julien_lacour » Mon May 31, 2021 10:32 am

Hello Stacey,

You can include a glossary as back matter by declaring it like this in the main bookmap:

Code: Select all

<bookmap>
    ...
    <backmatter>
        <booklists>
            <glossarylist href="maps/glossary.ditamap" format="ditamap"/>
            ...
        </booklists>
    </backmatter>
</bookmap>
Note: glossary.ditamap contains glossrefs to the glossgroup with all the glossentries:

Code: Select all

<map>
    <glossref href="../topics/glossary.dita#apsidal_precession" print="yes" keys="apsidal_precession"/>
    <glossref href="../topics/glossary.dita#perigee" print="yes" keys="perigee"/>
    <glossref href="../topics/glossary.dita#perihelion" print="yes" keys="perihelion"/>
</map>
Yours must be similar to mine (except the hrefs and the keys of course :D).

Could you try this on your side an tell me what problems are remaining after?

Regards,
Julien

Post Reply