index-see doesn't appear in webhelp output index

[cherbert]

The index-see element doesn't produce the desired results. What am I doing wrong?

Here is my prolog xml:

<prolog>
<metadata>
<keywords>
<indexterm>TDS<index-see>Temporal Data Store</index-see></indexterm>
<indexterm>Temporal Data Store </indexterm>
<indexterm>data storage</indexterm>
<indexterm>HAS<index-see>High Availability Store</index-see></indexterm>
<indexterm>High Availability Store</indexterm>
</keywords>
</metadata>
</prolog>

From the above I expected to see the following in the index:

TDS
see Temporal Data Store
Temporal Data Store [1]

HAS
see High Availability Store
High Availability Store [1]

However, this is what I see in the index:

TDS [1]
Temporal Data Store [1]

HAS [1]
High Availability Store [1]

[sorin_ristache]

Hello,

You are doing nothing wrong. The index elements added in DITA 1.2 like index-see and index-see-also are not supported yet in the Webhelp transformation, but we plan to add this support in a future version. We will let you know when we will add it.


Regards,
Sorin

[Alex Thornton]

Hi, In Oxygen XML Editor 24.1, I'm seeing the same problem in my Webhelp output. Has support been added for index-see?

[cosmin_andrei]

Hello,

We already have an issue on our internal issue tracker for it and I have added your vote for it. We will let you know when it will be implemented.

[susannecm]

Hi,
can you please add my vote?
Is it possible that the behavior has changed in 24.1 compared to version 20?

Code: Select all

<indexterm>Doxis webCube URLs<index-see>URLs</index-see></indexterm>

From this, I now get the following output:

Code: Select all

<span>Doxis webCube URLs URLs</span>

Is there a (short) way to exclude these indexterms from the WebHelp output while keeping them in the CSS-based PDF?
Kind regards
Susanne

[ionela]

Hi,

Sure, I have added your vote to this issue.
However, we have tested the behavior you have indicated on both versions v20 and v24.1 and we could not reproduce it. As a customization might generate this result, could you please try with the default transformation scenario and check if the problem persists.

Regards,
Ionela