"Locate" button is disabled in Index tab of CHM output

[khcy82nvh]

Hi guys

I used Oxygen to publish CHM output. The Locate button is disabled when I select a topic via"Index" tab; however, it is enabled if I select a topic via "Search" tab. Is it working mechanism of CHM, if not, any solutions for this issue?

Thanks a lot

Regards,

[sorin_ristache]

Hi,

The Locate button is disabled when the current page is not linked in the Contents tab. It does not matter if the current tab is Search or Index, if the current page from the right side panel is not displayed in the Table of Contents from the Contents tab then the Locate button is disabled because it cannot select that page in the Contents tree. This is normal behavior in CHM files.

If the current page is linked in the Contents tab but the Locate button is disabled please send us a working set of sample files (the input files of the Oxygen transformation) for reproducing the problem. Also please specify the term that you click on the Index tab for displaying the page for which the Locate button is disabled.


Regards,
Sorin

[khcy82nvh]

Thanks for your reply

I have sent a sample working copy to Technical Support of Oxygen to reproduce the issue.

I am looking forward to your solutions.

Regards,

[sorin_ristache]

Hi,

You are right, the Locate button is disabled when a topic is opened by a double click on a term in the list of index terms in the Index tab, even though that topic is linked in the Table of Contents (the Contents tab). The Locate button does not work correctly for the Index tab, although it always works correctly for the Search tab. Unfortunately the options in the Microsoft HTMLHelp compiler project file are undocumented (only some unofficial and incomplete documentation is available for HHP project files) and the values that we tried for the CHM toolbar buttons do not seem to fix the Locate button behavior for the Index tab. We hope to find a fix in the future for this minor annoyance.


Regards,
Sorin

[khcy82nvh]

Hi

Even though the Locate button is disabled when selecting an topic in Index tab, I still have some concerns.

For example, when I select a topic in Index tab, and switch to Content tab; in my opinion, the topic I have chosen previously in Index tab must be highlighted or reflected in Content tab. Am I correct about his assumption? However in reality, with the sample working set that I sent to Oxygen Technical Support, the topic I chose in Index tab are not highlighted or reflected in Content tab.

I am wondering whether I had defined <indexterm> incorrectly in DITA files.

Thanks

[sorin_ristache]

Hi,

For example, when I select a topic in Index tab, and switch to Content tab; in my opinion, the topic I have chosen previously in Index tab must be highlighted or reflected in Content tab. Am I correct about his assumption?

The topic must be highlighted in Content tab only if the switch from the Index tab to the Content tab is performed by pressing the Locate button. That assumes the Locate button is enabled when the current tab is the Index tab. Unfortunately this is exactly the problem (which we don't have a fix for, yet) with the CHM output file created by the DITA transformation: the Locate button is disabled when the current tab is the Index one.


Regards,
Sorin

[khcy82nvh]

Hi

I get it, finally.

Please get me informed when Oxygen has the batch to fix this problem.

Thanks for your valuable feedback

Regards,

[MarcelM]

Hi,

the reason for the 'Locate' button problem is a change in the file "...\dita-ot-3.3\plugins\org.dita.htmlhelp\xsl\map2htmlhelp\map2hhpImpl.xsl":
There is an Oxygen Patch:
<!-- OXYGEN PATCH START EXM-18626 -->
Auto Index=Yes
Binary TOC=Yes
Compatibility=1.1 or later
<!-- OXYGEN PATCH END EXM-18626 -->

If you switch back to
Binary TOC=No
the button works fine.

The original dita framework has no "Binary TOC" entry at all. So the default of the help compiler is used, which is "No".

Marcel

[Radu]

Hi Marcel,

Thanks for the feedback, I will add an internal issue to look into this, indeed we have these changes you found in the XSLT stylesheet, we made them a long time ago so we need to reconsider why we took that decision.

Regards,
Radu