Sorry about that. Yes, that portion of the plugin (v15) was customized. I set the code back to the default and it works as you describe. However, I do need to figure out how to use the topic title of the first topicref instead here. On a side note, can you explain this code that resides in the defau...

I have a ditabase topic that is a topicref in the frontmatter in my bookmap. The title of this topic contains a conref to a product name, followed by text. The purpose of course is to make this title the book title in my WebHelp output. In the WebHelp output, only the text displays in the top banner...

The information that you mention is controlled by the strings.xml file. Here's an excerpt from that file: <langlist> ... <lang xml:lang="es" filename="strings-es-es.xml"/> So, now what? You still haven't addressed the question of my OP: how is the strings.js created? I still can'...

What CMS application do you use? Astoria Do you have a WebHelp plugin installed in your CMS? Yes, we have a registered/licensed version of WebHelp Plugin installed on the CMS Did you install it or it came already installed by the CMS installation kit? Astoria administrator installed it. What is the...

I updated the localized strings file for spanish (strings-es-es.xml) and uploaded to our CMS, and created the WebHelp output, but the strings.js file still contains the old values.

How do I get the strings.js file updated?

Thanks for the link to the download, but this plugin has been customized to such a degree that I cannot upgrade at this time. Plus, I'm trying to meet a critical deadline. :wink: After much troubleshooting, I narrowed down the issue to the com.oxygenxml.webhelp\xsl\dita\dita2webhelp.xsl file. Under ...

Thanks for the file, Sorin. Without changing any of my input settings, this didn't fix my problem. However, if I specified the -Dargs.default.language=$LOCALE%, where %LOCALE% is the current language, then the two variables emits properly. My source files (all of them) have the @xml:lang attribute s...

I thought that the reason the WebHelp plugin provides the variables files (.\com.oxygenxml.webhelp\oxygen-webhelp\resources\localization\*.xml) is to provide localized words and phrases for translated output. However, the webhelp_topic.js contains the English phrase "With Frames" (line 60)...

It's been nearly 2 years since a reply has been posted about enhanced search for WebHelp. Have there been any improvements with Search? I noticed that the previous reply mentioned the addition of Boolean search capabilities. However, when I try this search, boot AND shoes, AND is included in the sea...

I've been asked for the browser requirements for WebHelp output, but I can't find this information. Where can I find what web browsers are supported with WebHelp and WebHelp for Mobile?

Thanks.

I have 15.1 installed, but more importantly, we are processing our books on a CMS. So, the patch fix would work better for our environment.

Footnotes in our WebHelp output are not linking correctly. When I select the footnote link, the browser tries to open a new tab and never resolves the link. I'm running the licensed WebHelp plugin from a CMS system, not locally. Here's the URL that the browser trying to open (snipped) http://.../adm...