Search found 86 matches
- by urbanrobots
- Fri Apr 01, 2016 9:26 am
- Forum: Feature Request
- Topic: Resolve abbreviated-form and term in Webhelp related-links
- Replies: 4
- Views: 2951
Resolve abbreviated-form and term in Webhelp related-links
Hello. I believe that this is a DITA-OT bug. We thought that the Webhelp 17.1 plugin solved this, but <abbreviated-form> and <term> used for glossary entries still do not correctly resolve in HTML output. For example, this input file's title: <title>Keyword (<keyword keyref="g_etsi"/>) Ter...
- by urbanrobots
- Fri Apr 01, 2016 9:08 am
- Forum: Other Issues
- Topic: customizing for related topic output
- Replies: 5
- Views: 4150
Re: customizing for related topic output
Outside of XSLT, you can use @type = "topic" in the DITA source reltable to override the concept, reference task organization. By specifying topic, all links are organized under a "Related information" heading.
Take care,
-Nick
Take care,
-Nick
- by urbanrobots
- Thu Mar 31, 2016 7:50 am
- Forum: Other Issues
- Topic: Webhelp file structure
- Replies: 1
- Views: 1326
Webhelp file structure
Hello - We notice that the webhelp output shows the file hierarchy of our CMS. Is there any way to flatten this and/or hide the file structure from readers? For example: oxygen-webhelp repositories .... | master .........| documentation ...............| product_category .....................| produc...
- by urbanrobots
- Fri Mar 25, 2016 6:16 pm
- Forum: XSLT and FOP
- Topic: Webhelp XSLT glossentry override
- Replies: 6
- Views: 3817
Webhelp XSLT glossentry override
Hi, Where do we configure the glossary output structure for glossary entries in the Webhelp XSL files? For the PDF plugin, we use the following template and FO blocks. We'd like to do something similar in the Webhelp plugin. <xsl:template match="*[contains(@class,' glossentry/glossentry')]"...
- by urbanrobots
- Fri Mar 25, 2016 5:37 am
- Forum: XSLT and FOP
- Topic: Webhelp code highlighting in 17.1 is not backwards compatible
- Replies: 3
- Views: 2247
Re: Webhelp code highlighting in 17.1 is not backwards compatible
Hi Bogdan, The problem existed in the plugin_commons.xml file. It took a while to figure this out, but copying these lines from Oxygen Webhelp 17's plugin_common.xml file to Oxygen Webhelp 17.1's plugin_common.xml file seemed to get the highlighting to work in 17.1 output. <feature extension="d...
- by urbanrobots
- Fri Mar 25, 2016 5:32 am
- Forum: Common Problems
- Topic: WebDAV timeout issue
- Replies: 6
- Views: 3820
Re: WebDAV timeout issue
Thanks! I let the user know, and it doesn't seem to be happening anymore... but let's see how thing go.
Take care,
- Nick
Take care,
- Nick
- by urbanrobots
- Wed Mar 23, 2016 5:07 am
- Forum: Common Problems
- Topic: WebDAV timeout issue
- Replies: 6
- Views: 3820
WebDAV timeout issue
Hello, Oxygen - Our users connect to a CMS using WebDAV connections. Sometimes, people receive this error message: Cannot open the specified file: Timeout waiting for connection from pool (https://<file_path>) Would you like to open it as a regular file? If the user restarts Oxygen XML Editor, the p...
- by urbanrobots
- Tue Mar 22, 2016 8:43 am
- Forum: XSLT and FOP
- Topic: Webhelp code highlighting in 17.1 is not backwards compatible
- Replies: 3
- Views: 2247
Webhelp code highlighting in 17.1 is not backwards compatible
Hello. We recently upgraded to Oxygen Webhelp 17.1. We use DITA-OT 17.1 and notice that upgrading to Webhelp 17.1, without making any other changes, results in code highlighting not working. If we re-implement the Oxygen 17.1 Webhelp, then the code syntax highlighting works fine again. What are we d...
- by urbanrobots
- Tue Mar 01, 2016 7:54 pm
- Forum: Common Problems
- Topic: SQF adds invalid xmlns value in keyword
- Replies: 3
- Views: 1963
Re: SQF adds invalid xmlns value in keyword
Thank you! That worked.
- by urbanrobots
- Sun Feb 28, 2016 10:45 am
- Forum: Common Problems
- Topic: SQF adds invalid xmlns value in keyword
- Replies: 3
- Views: 1963
SQF adds invalid xmlns value in keyword
Hello, I am new to SQF, so my syntax may be incorrect. I would like to replace plaintext strings with associated <keyword> elements. For example, look for "product name" and replace it with "<keyword keyref="prod_name" /> ". Using SQF, I tried this: <pattern> <rule id=&...
- by urbanrobots
- Fri Sep 11, 2015 8:18 pm
- Forum: Common Problems
- Topic: glossary keyrefs not appearing in ToC
- Replies: 5
- Views: 2184
Re: glossary keyrefs not appearing in ToC
Awesome. Thanks, Radu.
Just to confirm, this issue will be fixed in the standalone webhelp?
The <abbreviated-form> element also does not render in the DITA Maps Manager in Oxygen 17 Editor (even through they publish fine in PDF). Will this be fixed as well?
Take care,
- Nick
Just to confirm, this issue will be fixed in the standalone webhelp?
The <abbreviated-form> element also does not render in the DITA Maps Manager in Oxygen 17 Editor (even through they publish fine in PDF). Will this be fixed as well?
Take care,
- Nick
- by urbanrobots
- Wed Sep 09, 2015 6:41 pm
- Forum: Other Issues
- Topic: context-sensitive help links break in Chrome and IE
- Replies: 3
- Views: 2199
Re: context-sensitive help links break in Chrome and IE
Hi, Bogdan -- Thanks for the information. I like how the user does not need to interact with an error message to access the webhelp. However, this does not solve the problem of context-sensitive links. If you try to directly access a file that is not index_frames.html, does the webhelp load the page...
- by urbanrobots
- Wed Sep 09, 2015 12:37 am
- Forum: Other Issues
- Topic: context-sensitive help links break in Chrome and IE
- Replies: 3
- Views: 2199
context-sensitive help links break in Chrome and IE
Hello, If a person views the webhelp in Chrome or IE, the webhelp links break after they click OK to the error about JavaScript. Is there any way to suppress this error message and automatically load the frameset version of the webhelp? We want to be able to link to any page in the webhelp no matter...
- by urbanrobots
- Wed Sep 09, 2015 12:23 am
- Forum: Other Issues
- Topic: print webhelp footer
- Replies: 4
- Views: 1850
Re: print webhelp footer
Oops. I had a typo in the file. This CSS works perfectly. Thanks!
- by urbanrobots
- Mon Sep 07, 2015 6:01 pm
- Forum: Other Issues
- Topic: print webhelp footer
- Replies: 4
- Views: 1850
Re: print webhelp footer
Thanks for the reply, Bogdan.
This works for printing the copyright footer in the ToC area, but does not work for the footer that appears under the content itself. Is JavaScript limiting the CSS functionality?
Thanks,
- Nick
This works for printing the copyright footer in the ToC area, but does not work for the footer that appears under the content itself. Is JavaScript limiting the CSS functionality?
Thanks,
- Nick
- by urbanrobots
- Sun Sep 06, 2015 9:56 pm
- Forum: Other Issues
- Topic: print webhelp footer
- Replies: 4
- Views: 1850
print webhelp footer
Hello,
We use the webhelp.footer.file parameter to add a footer to each HTML topic. However, this footer does not print. We need copyright information on each printed page. Can you explain how to do this?
Thanks!
Take care,
- Nick
We use the webhelp.footer.file parameter to add a footer to each HTML topic. However, this footer does not print. We need copyright information on each printed page. Can you explain how to do this?
Thanks!
Take care,
- Nick
- by urbanrobots
- Thu Sep 03, 2015 7:58 am
- Forum: Common Problems
- Topic: glossary keyrefs not appearing in ToC
- Replies: 5
- Views: 2184
glossary keyrefs not appearing in ToC
Hi, thanks in advance for your help. Using the Webhelp output, <abbreviated-form> and <term> elements with keyrefs to glossary terms work fine in most places. However, the ToC does not show them. The element show up as nothing in the TOC HTML on the left navigation area. Here is an example: The ToC ...
- by urbanrobots
- Sat Aug 29, 2015 8:05 pm
- Forum: DITA (Editing and Publishing DITA Content)
- Topic: Problem with DITA Webhelp in Chrome
- Replies: 8
- Views: 4472
Re: Problem with DITA Webhelp in Chrome
Does Oxygen plan to support a local version of the webhelp that works in Chrome? We have the same problem of supplying a webhelp folder to customer who will download and look at the html files locally. We don't know what browsers they will use. Also, is there any way to change the frames so that the...
- by urbanrobots
- Sat Aug 29, 2015 7:51 pm
- Forum: Feature Request
- Topic: Make Web Help Context Help work without JavaScript
- Replies: 3
- Views: 3334
Re: Make Web Help Context Help work without JavaScript
We also experience issues with JavaScript browser support. We tell people to use FF or Chrome, but our users in China mostly use IE.
Any chance that this will be updated to an optional configuration in a later release?
Thanks,
- Nick
Any chance that this will be updated to an optional configuration in a later release?
Thanks,
- Nick
- by urbanrobots
- Fri Jun 05, 2015 9:46 pm
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
Hi Radu, Great. Using the standard version of DITA-OT 2.1.0 M1 and the simplified command line execution part seemed to do the trick. The missing "s" was just a copy-paste issue. I have a different issue with key references for topicrefs not resolving for files in different folders than th...
- by urbanrobots
- Fri Jun 05, 2015 10:08 am
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
Hi Radu, Thanks for the ideas. It's still not working... I tried the following variations to no success: - Java 1.8, Saxon 9.1 - Java 1.8, Saxon 9 - Java 1.7, Saxon 9.1 - Java 1.7, Saxon 9 Here is the dita.bat file for Java 1.7 and Saxon 9.1: @echo off REM Oxygen Webhelp plugin REM Copyright (c) 199...
- by urbanrobots
- Fri Jun 05, 2015 7:53 am
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
Hi Radu, Thanks. Unfortunately, that opens up another problem. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\>C:\OxygenWebHelp\DITA-OT2.0.1\plugins\com.oxygenxml.webhelp\dita.bat Buildfile: C:\OxygenWebHelp\DITA-OT2.0.1\build.xml init: check-a...
- by urbanrobots
- Wed Jun 03, 2015 5:03 pm
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
Hi, again, Radu: Here is the dita.bat file in the com.oxygen.webhelp plugin folder that I updated and with the environmental variable data and have been trying to run: @echo off REM Oxygen Webhelp plugin REM Copyright (c) 1998-2015 Syncro Soft SRL, Romania. All rights reserved. REM Licensed under th...
- by urbanrobots
- Wed Jun 03, 2015 4:42 pm
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
Hi Radu, Yes. I'm using the latest DITA-OT. Here are the details: - DITA-OT 2.0.1 - Oxygen Webhelp 17 build id: 2014102117 (with the plugin_2.xml file) - JDK 1.8.0_45 - Saxon 9-1-0-8j Looking through the error message, the build.xml:47 issue is here at webhelp-index: <target name="output" ...
- by urbanrobots
- Mon Jun 01, 2015 5:56 pm
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
I'm also getting a BUILD FAILED! issue with DITA-OT 2.0 show a java.lang.NoSuchMethodError problem. Any thoughts on how to fix this? [b]Here is the output:[/b] Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\>C:\OxygenWebHelp\DITA-OT2.0.1\plugin...
- by urbanrobots
- Sun May 03, 2015 7:40 pm
- Forum: Other Issues
- Topic: Build Failed! with external DITA-OT 2.0
- Replies: 15
- Views: 9005
Re: Build Failed! with external DITA-OT 2.0
I'm trying to do the same thing with the same Oxygen version, but get this error. Executing: "/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java" -Xmx384m "-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.ditang.relaxng.defaults.RelaxDefaultsParserConfi...
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service