Webhelp glossary tooltips appear with line breaks

[urbanrobots]

Hello. For the tooltips that appear over <abbreviated-form> elements in HTML output, it appears that the line breaks that appear in

Code: Select all

<glossdef>

are preserved. This means that the tooltips look very scrambled. Is there any way to fix this?

Here is an example input:

Code: Select all

<glossdef>A standard for

        describing a sound system with front, surround, and overhead channels. The first 

        numeral represents the number of front channels, the second represents the number of surround

        channels, and 

        the third represents the number of height channels. For example, 3/2/2

        indicates that there are three front channels, two surround channels, and two height

        channels.</glossdef>

Will end up looking like this in output:

Code: Select all

A standard for

        describing a sound system with front, surround, and overhead channels. The first 

        numeral represents the number of front channels, the second represents the number of surround

        channels, and 

        the third represents the number of height channels. For example, 3/2/2

        indicates that there are three front channels, two surround channels, and two height

        channels.

However, we'd ultimately like the tooltip to look like this:

Code: Select all

A standard for describing a sound system with front, surround, and overhead channels. The first  numeral represents the number of front channels, the second represents the number of surround channels, and  the third represents the number of height channels. For example, 3/2/2 indicates that there are three front channels, two surround channels, and two height channels.

Thanks for your help.

Take care,
- Nick

[Radu]

Hi Nick,

So you have an abbreviated-form element with a keyref to a glossentry, something like that, right?
I cannot reproduce the problem, what version of the DITA OT are you running, is it an external DITA OT or a DITA OT bundled with Oxygen?
At some point I remember there was such a problem and it was fixed in DITA OT 2.x:

https://github.com/dita-ot/dita-ot/issues/1759

and we also had the fix in the DITA OT 1.8 bundled with Oxygen but if you are using an external DITA OT 1.8, you should perform the fix yourself in it.

Regards,
Radu

[urbanrobots]

Perfect. Thanks, Radu. That worked like a charm. We're using DITA-OT 1.7.5 due to how it handles topicref keyrefs. I guess we should probably start to investigate implementing 2.0 though.