Search found 10 matches

by MelkorX
Sat Jul 27, 2019 8:10 am
Forum: DITA (Editing and Publishing DITA Content)
Topic: WebHelp v17 issue with Firefox 68.0 when viewed locally
Replies: 2
Views: 1099

Re: WebHelp v17 issue with Firefox 68.0 when viewed locally

Thank you. Unfortunately I'm stuck with 17 for a bit due to compatibility with our CCMS, but I'll be upgrading both our CCMS and WebHelp plugin version soon.
by MelkorX
Tue Jul 23, 2019 8:04 pm
Forum: DITA (Editing and Publishing DITA Content)
Topic: WebHelp v17 issue with Firefox 68.0 when viewed locally
Replies: 2
Views: 1099

WebHelp v17 issue with Firefox 68.0 when viewed locally

Hello, We have a recent issue that appeared after upgrading to Firefox 68.0. When the WebHelp generated from the v17 plugin is opened, only the ToC is visible. Perhaps this is related to the following Firefox fix: https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730 Is this ...
by MelkorX
Thu Jun 22, 2017 11:55 pm
Forum: Common Problems
Topic: Find/replace newline
Replies: 2
Views: 2350

Re: Find/replace newline

Thanks Radu. I had to add \t as well to the regular expression, and then it worked.
by MelkorX
Thu Jun 15, 2017 2:46 am
Forum: Common Problems
Topic: Find/replace newline
Replies: 2
Views: 2350

Find/replace newline

I am trying to remove extra spaces at the beginning and end of <codeblock> elements in DITA files. For example: <codeblock> codeExample ce = new codeExample(); ce.someFunction(); </codeblock> should be <codeblock>codeExample ce = new codeExample(); ce.someFunction();</codeblock> I'm having trouble a...
by MelkorX
Fri Aug 12, 2016 9:13 pm
Forum: SDK-API, Frameworks - Document Types
Topic: XSLT from 15.2 SDK
Replies: 2
Views: 3012

Re: XSLT from 15.2 SDK

Hi Alex, I was able to get it working with 15.2 using the Saxon API directly. final TransformerFactory tfactory = new TransformerFactoryImpl( net.sf.saxon.Configuration.makeLicensedConfiguration(null, "com.saxonica.config.EnterpriseConfiguration")); Another thread in this forum pointed me ...
by MelkorX
Thu Aug 11, 2016 11:47 pm
Forum: SDK-API, Frameworks - Document Types
Topic: XSLT from 15.2 SDK
Replies: 2
Views: 3012

XSLT from 15.2 SDK

Hi, I'm developing a plugin with the 15.2 SDK. I want to run a series of XSL transformations on the current file. It looks like API support to do this has been added for the 18 version of the SDK. Is there any way to do this for 15.2? I've tried just running Saxon from the command line but get the e...
by MelkorX
Fri Feb 05, 2016 1:27 am
Forum: Common Problems
Topic: Nav buttons missing in Oxygen Webhelp output
Replies: 5
Views: 2101

Re: Nav buttons missing in Oxygen Webhelp output

It is definitely possible. I am taking over work from a contractor. They had said there was a javascript issue, but that does not seem to be the case. We wanted the navigation buttons for all topics, so I updated the template match in maplinkNextPrevFullIteration.xsl to not filter for @collection-ty...
by MelkorX
Thu Feb 04, 2016 12:01 am
Forum: Common Problems
Topic: Nav buttons missing in Oxygen Webhelp output
Replies: 5
Views: 2101

Re: Nav buttons missing in Oxygen Webhelp output

I saw the buttons in the output html source. Turns out the visibility was set to hidden for .navparent,.navprev,.navnext in the webhelp_topic.css. I commented out the visibility:hidden line and it seems to work when using the collection-type="sequence" on the topicref. Thanks for the tip!
by MelkorX
Wed Feb 03, 2016 11:43 pm
Forum: Common Problems
Topic: Nav buttons missing in Oxygen Webhelp output
Replies: 5
Views: 2101

Re: Nav buttons missing in Oxygen Webhelp output

Thanks for replying. I tried setting collection-type="sequence" on the top-level topicref in the map and still do not see navigation buttons.
by MelkorX
Wed Feb 03, 2016 1:40 am
Forum: Common Problems
Topic: Nav buttons missing in Oxygen Webhelp output
Replies: 5
Views: 2101

Nav buttons missing in Oxygen Webhelp output

We are using the standalone Oxygen WebHelp 17.0 plugin and cannot get the Previous Topic, Next Topic buttons to appear. I have heard this is a limitation with the standalone plugin. Is that true? Is there any way to get the navigation buttons to appear?