Hi Jonas,

Unfortunately, the current oXygen XML WebHelp implementation does not offer extension points for JavaScript files.
Also, as SearchCommon.js contains core functionally for the search engine, we do not recommend the modify/customize this file.

Regards,
Ionela

Hi,

I've added your comments to our issue tracking tool, so we'll contact you by email when a nightly build contains this bugfix.

Regards,
Ionela

Hello,

Thank you for feedback.

I confirm this is a bug in the current WebHelp Responsive implementation. I have logged it to our issue tracking tool in order to be analyzed and resolved by our development team.
We'll update the thread when the bugfix becomes available.

Regards,
Ionela

Hi, Are using version 20.1 of oXygen XML? Regarding the first issue you have indicated, could you please specify if you have the attribute chunk="to-content" set for category1 and category2 topics ( e.g. Apps And Accounts )? If yes, in order to generate to the TOC also the third level topi...

Hello,

Thank you for your feedback.

We are aware of this issue and it is already resolved in our current development stream. We'll update the thread when the bugfix becomes available.

Regards,
Ionela

Hello, I've tested and you could achieve this using a custom CSS file with the following CSS code: h1:before{ content: url('logo.png'); } More information about how to use a custom CSS can be found in our user manual: Referencing the Custom CSS Taking into account that the image URL should be relati...

Hello, The WebHelp output top menu is static, this means that it does not change when a certain topic is opened (selected). Given this, for a publication output you'll have a certain text in top menu for any page of this documentation. To change the search background image you can develop a CSS cust...

Hello, I'm not sure I have correctly understood your request. When a topic is selected it is highlighted in the breadcrumb and the publication TOC. For example, in our documentation if you select Developer Reference > Publishing Templates > Publishing Templates Gallery : https://www.oxygenxml.com/do...

Hi Mona, Indeed, in the localization files ( e.g. Strings-en-us.xml) is present only the table label not also the period. The period is added from the XSLT stylesheets used to process the input when the transformation scenario is run. To may achieve this customization using XSLT extension points: ht...

Hi Ann, Unfortunately, we do not have a tool that can provide these details for the WebHelp output (tracking the visited pages, searched keywords, etc). I have logged your feedback as an improvement request to our issue tracking tool to be further analyzed. You might obtain this information by using...

Hi, To check this on our side could you please let us know how you refer the file in the publishing template, from an HTML fragment extension point or by using a parameter? Could you please provide us the code from the .opt file where you point to the menu.html file? As a general rule make sure that...

Hi, Unfortunately, there isn't an easy default way to achieve using a parameter so something similar. There is a parameter in the D ITA Map WebHelp Responsive transformation scenario named ' webhelp.show.child.links ', but if it is set to ' yes ' the child links component appears for all topics (not...

Hi.

In the WebHelp Responsive output generated with oXygen XML v20.1 we already have this functionality (Go to Top, Home and Breadcrumb navigation). Please check this screen-shot:
Home Top Navigation

Regards,
Ionela

Hi, Indeed, the navigation links are by default hidden on mobile devices. I have added an improvement request to our issue tracking tool in order to reanalyze this. However, using Oxygen XML v20.1 you could achieve the result you need following these steps: Save you favorite template as explained he...

Hello, You can achieve this using a CSS customization for your WebHelp Responsive output. You can find the guidelines about how you can customize the output using CSS in our user manual: https://www.oxygenxml.com/doc/versions/20.1/ug-webhelp-responsive/topics/webhelp-customizing-with-css.html For ex...

Hi, Thank you for your feedback. Indeed, this is a bug in the current oXygen XML WebHelp implementation. I have logged it to our issue tracking tool in order to be resolved in a future version. As a workaround, you can use a CSS as follows: .wh_tile_title { line-height: 1.7em; } Then, reference the ...

Hi, Using oXygen XML v20.1 you could achieve this following these steps: Save you favorite template as explained here: https://www.oxygenxml.com/doc/versions/20.1/ug-webhelp-responsive/topics/whr-create-publishing-template.html . Note that you need to check the " Include HTML Page Layout Files ...

Hi,

Thank you for your feedback.
I was able to reproduce this problem on our side and I've logged it to our issue tracking tool in order to be resolved in a future version of oXygen XML.

Regards,
Ionela

Hi,

Just to update the thread, this error occurred when the ditamap does not contain any reference to a topic which is not valid use-case for a production environment.

Regards,
Ionela

Hello,

Unfortunately, this is currently not possible. The updated topics may have references to other topics or to other elements from the ditamap, so it is not possible to update just the modify content and its references.

Regards,
Ionela

Hi Antti,

You are right, we'll mention this too in our documentation. Thank you for your suggestions.

Regards,
Ionela

Hello, Regarding the navigation issue you've indicated a possible workaround would be to use the ' webhelp.publication.toc.links ' parameter set to ' all ' for the DITAMap WebHelp Reponsive transformation scenario. The default value of this parameter is ' chapter ', but if you change its value to ' ...

Hi, Thank you once again for your feedback. We do not plan to completely remove the DITAMap WebHelp Classic transformation scenario (at least not on the short term). We've just marked the scenario as deprecated as it won't be further improved and we would like to encourage our users to switch to the...

Hello, Thank you for your feedback. We have decided to focus our resources on the development and enhancement of the WebHelp Responsive output generation rather than the Classic one. The DITA Map WebHelp Classic transformation scenario is included in the oXygen XML Editor/Author, but we won't add fu...

Hello, The index.xml file is used to collect the indexterms from the ditamap, so this file cannot be skipped during the WebHelp Responsive output generation. However, we are not aware of these kind of errors. Do you run the default DITA Map WebHelp Responsive transformation scenario or a customized ...

Hi Benjamin, You are using the DITA Map PDF transformation scenario, right? I have tested in a default installation of oXygen XML v19.1 with the built-in DITA-OT 2.x on our sample project flowers.ditamap and I could not reproduce this issue. I have added in a topic two sections one with indexterm an...

Hello,

You refer to the top menu (main menu from the top of the page)? If yes, we have a topic in our user manual that described how you can hide some topica from the menu entries:
https://www.oxygenxml.com/doc/versions/ ... -menu.html

Regards,
Ionela

Hi, Thank you for your feedback. We could reproduce this problem on our side and I have logged it to our problem tracking tool to be further investigated. However, the issue might be triggered from DITA-OT engine as we get the same behavior when we run the DITA Map XHTML scenario (this is the built-...

Hello, Thank you for your feedback. Unfortunately, in the current version of oXygen XML WebHelp there is no predefined way to achieve this functionality. We have a similar request logged to our issue tracking tool and I've added your feedback to it in order to be further analyzed. However, most like...

Hello, Thank you for your feedback. Unfortunately, there isn't a way to highlight only the search phrase in the returned results and ignore the individual words (when performing exact search). I have logged this as an improvement request to our issue tracking tool in order to be further analyzed by ...