Hi, We chose to generate duplicate HTML files, because each instance of the topic file should have it's own correct navigation links in the output (more specific, the links from the publication TOC, topic breadcrumb and menu). To differentiate them in the publication, we enforce this through the &qu...

Hi, Unfortunately, besides the ID unicity issue, this would also involve renaming any topic file references. There is no predefined support for such use-case in the WebHelp product. As we are not aware of such possibility, so I'm afraid that we could not help with any advise. Like I previously menti...

Hi, We consider that using the ID from the root element of the topic as file name is not possible. However, as this is more a DITA related questions, rather than an oXygen one, you should give it a try and raise the question on the DITA Users lists (https://groups.google.com/g/dita-ot-users?pli=1 an...

Hi Leroy, Indeed, the tables from the WebHelp Responsive output have variable width, in order to keep the responsiveness of the topics. So, depending on the screen and viewport size, the columns may compress or extend. That's achieved by a width:100%; property, which is set on all tables by the defa...

Hello, Indeed, we decided to display all permalinks in the output, as there are users that found that helpful. However, I've logged an improvement request also for this aspect, so we will see if we could implement something to make this controllable (through a dedicated transformation scenario param...

Thank you for the suggestion!
We will consider this in a future version of oXygen.

Regards,
Costin

Hi Graham,

I've added your comment, as-is on the issue.

Regards,
Costin

That's the same improvement request - for faceted search, that we logged.
Added your comment there.

Regards,
Costin

Hi,

Yes, we have this logged and I've added your comment to it.

We will let you know when this functionality will become available.

Regards,
Costin

Hi Graham, Unfortunately, in the current implementation of WebHelp, it is not possible to set keyboard shortcuts for the previous/next topic links in the WebHelp Responsive output. However, it may be possible to implement your own shortcuts, using a JavaScript customization of your own. You could ad...

Hi Graham, Sure thing! If you are licensed to use the plugin, that means that you have a license of the specific product type - Author or Editor or Developer (depends on the product type that appears as tjhe "Component" field on your license key). And you may indeed use both the plugin and...

Hi maglid,

I have just updated the issue that we have logged in our internal tracking system with your latest feedback.

Regards,
Costin

Hello, In content, Oxygen XML WebHelp does not have capability to generate links without the .html extension and does not autimatically route them. The routing could be most probably performed by the HTTP server that hosts your WebHelp Responisve, so you should look into configuring the server to co...

Hi Leroy, Adding a button to hide the topic toc is not somthing you could do by default using the current implementation of webhelp. However, I logged an improvement request in our internal tracking system, so our development team will consider adding a button to expand/collapse the toc in a future ...

Hi, Thank you for the feedback! With the default implementation of WebHelp, it is not possible to remove the elements from being printed. I've just logged an improvement request in our internal tracking system, so that our developers will try to improve this (remove any unnecessary elements from the...

Hi, This kind of issues may occur when there in the source files that you are using which are outside the folder of the main DITA Map. More specific, the DITA OT is known to have some issues when there are resources (topic references, other submaps, or any other resources) that are located outside o...

Hello, You have an older version of Author - version 20 - which worked with an older version of DITA (2.x), that is bundled with it. The latest version uses DITA OT 3.x (it comes bundled with DITA OT 3.4.1 more specific). To answer your other question, no, you could not use the WebHelp plugin that c...

Hi pahom, Please note that the WebHelp Classic transformation scenario became deprecated 2 versions ago and, currently, we only implement small fixes, but it will be most probably dropped in the near future versions of oXygen. So, as long as you do not have a specific reason to use the deprecated We...

Hi Copley, This issue - WebHelp transtype not recognized - usually occurs if the WebHelp plugin was not integrated correctly in the DITA-OT that you are using locally. If you are using the WebHelp DITA-OT plugin to publish WebHelp from command line (outside of the oXygen GUI), please make sure that ...

I've also replied on the email you sent us, but I will post my reply here as well: The navlinks should work by default, if you set the show.navigation.links parameter. You should not do any other change over the plugin or the template. I suggest you should download and deploy a clean copy of oXygen ...

Hello, We are not aware of such issues and we could not reproduce it. The only thing we could think about is that you should make sure that the input method you are using is English (or a variation of English). That's because using a keyboard input layout in a different language could use some speci...

Hello, The issue related to the search remaining in loop, when using Japanese language on a DITA Map published to WebHelp was already fixed in a maintenance build of the version 22. Therefore, if you download, install and use the latest version 22.1 available on our website, thearch should not remai...

Hi Michael, I've already replied on the comment you left on our User-Guide, so I am pasting here the reply. This may occur if the XML that contains the HTML / Javascript resources is not well formed (for example, if the fragment contains special characters that could break well-formedness). You can ...

Hi shrinidhiha, How exactly are you using WebHelp? Are you using the standalone WebHelp plugin product from our website, or are you a custom DITA-OT using the WebHelp plugin that you extracted from an Oxygen XML GUI product (like Editor or Author)? We double checked and the standalone WebHelp plugin...

Hi Catherine, I'm afraid that we do not have any guidelines to start up with using Jenkins or other CI systems. Also, we only develop Oxygen products and can help with issues related strictly to using them, but we do not offer any training or consultancy services. We suggest you should reach to a co...

Hi, I'm afraid that, currently, the only way to generate PDF for the WbHelp output is the one that you already found. We have an improvement request logged in our internal tracking system to make it possible to generate PDF on the fly for the WebHelp output. Our development team will analyze the iss...

Hi Bob, Actually, the "webhel.custom.resources" parameter is available by default also for the DocBook WebHelp Classic transformation scenario as well, like you can see in the screenshot below (I double checked on the latest version 22.0 of oXygen XML Editor). https://i.ibb.co/7W8qKkT/Cust...

Hi, Indeed, the XPath is applied for each topic in the root map. However, in this case, you could run the XPath on the expanded DITA Map that contains the submaps and their topicrefs. Such a DITA Map is available in the temporary folder created at transformation runtime. In order to keep that map av...

Hi, The CSS rules do not apply on the output, because there are other CSS selectors coming from the default CSS files that are more specific than the ones you are using. You could notice which selectors match the elements in the output, by inspecting the CSS behind the HTML pages, using your interne...

Hi awrlv, You could open the main DITA Map - the parent Map that contains all other subamaps, then set the scope for your Xpath to the current DITA Map hierarchy. The scope can be set either from the Xpath toolbar - there's a small widget that looks like a file with down pointing arrow at the left s...