Hi Dirk, Indeed you need two java implementations, one for the editor and one for the renderer. When you open the XML document and you just scroll through it or work without interacting with any form control in the page, the renderers will be used to visually present the form control in the document...

Hi, You can see right here the contents of an obfuscated stylesheet: http://www.cranesoftwrights.com/resources/Crane-UBL-Skeleton/Crane-UBL-Skeleton-obfuscated.xsl So you could try to contact Ken Holman and find out more details about how he does that: http://www.cranesoftwrights.com/contact.htm Reg...

Hi Carole, When you want to create separate lines with XSL-FO you need to add an fo:block around that area, something like: <xsl:variable name="pubDate"> <fo:block> <xsl:value-of select="(/*/opentopic:map//*[contains(@class, ' topic/revised ')]/@modified)[1]"/> </fo:block> <fo:bl...

Hi Carole,

You were right about the quotes, whenever you already have double quotes around an attribute value, you must use single quotes inside it. The XML specification does not allow nesting double quoted.
And thanks for the kind words.

Regards,
Radu

Hi Nick, I think we are on the right track. About this remark: Java 1.6 also throws an error. A major.minor version 51 error related to the ExtensibleAntInvoker. Despite my efforts to prevent that, the DITA Open Toolkit 2.0 main JAR library file was compiled with Java 1.7 compatibility: https://gith...

Hi Carole,

Here's my suggestion:

1) You leave the commons.xsl as it is, without any changes.
2) In the custom.xsl you use this construct:
Regards,
Radu

Hi,

I answered you here:

http://www.oxygenxml.com/forum/post34219.html

Regards,
Radu

Hi, You could for example store the XSLT on an HTTP server with certain authorization requirements. But if the user would have the authorization details he could still open the XSLT from that URL. The Saxon 9 processor also allows you to compile an XSLT stylesheet: http://saxon.sourceforge.net/saxon...

Hi Nick, Instead of adding REM before the line: REM -lib "%DITA_OT_INSTALL_DIR%\plugins\com.oxygenxml.webhelp\lib\dost-patches-DITA-1.8.jar"^ please try to remove it completely. The command line a very long line which is split using ^ and but the Windows batch processor still interprets it...

Hi Bill,

Right, once an element is considered space preserve by Oxygen, pressing ENTER inside it will present first the option to add a line break and then the option to split it.

Regards,
Radu

Hi Scott,

You can see what each of those manifest parameters means here:

http://docs.oracle.com/javase/7/docs/te ... ifest.html

Regards,
Radu

Hi Carole, Just as an example, the productName variable is defined in: OXYGEN_INSTALL_DIR/frameworks/dita/DITA-OT/plugins/org.dita.pdf2/xsl/fo/root-processing.xsl as: <xsl:variable name="productName"> <xsl:variable name="mapProdname" select="(/*/opentopic:map//*[contains(@cl...

Hi Scott, So you are interested in Text-only editing, you are creating no Author visual editing mode, right? Please see a comment for each JAR library below along with advice for removing/keeping it: batik-anim-1.7.jar (render SVG in Author, advice->remove) batik-awt-util-1.7.jar (render SVG in Auth...

Hi Nick,

Have you tried to edit the dita.bat script we ship with the WebHelp plugin and remove from it the reference to the dost-patches-DITA-1.8.jar library?

Regards,
Radu

Hi Pat, There is already an issue registered on the Batik issues list: https://issues.apache.org/jira/browse/BATIK-1112 The problem is that your SVG contains Inkscape extensions in it, including in the CSS properties and Batik chooses to ignore all other CSS properties after such a property that it ...

Hi Scott, Indeed the line in the properties file is automatically broken if it overflows a number of characters. So that should be OK. I'm not really sure what the problem is, just for tests could you modify in the build-trusted.xml the values for Caller-Allowable-Codebase and Application-Library-Al...

Hi Patrik,

If you attach to an email the base.framework and the extended.framework then give me some details about the problem I could try to look into this. It could either be a bug or a limitation of the extension mechanism.

Regards,
Radu

Hi Chris, We could consider adding API for this (possibly in Oxygen 17.1 we'll release in the Autumn of 2015). I would need more details about your CMS integrations. So how do users usually publish? They open a DITA Map in the Oxygen DITA Maps Manager view and use a custom toolbar button you have co...

Hi Chris, When users apply a profiling attribute set in the DITA Maps Manager view and publish, we dynamically create a DITAVAL file from the current applied profiling attribute set and send it as a parameter to the DITA Open Toolkit processing. But unfortunately we do not have an API way of allowin...

Hi Frank,

Thanks for the update.

Regards,
Radu

Hi Scott, I am not sure why those crashes occurred, did you find any meaningful information in the Java console view? From what I remember, when the Javascript code calls the applet code, it calls it with restrictive security permissions so we elevated the rights in the Java code. An alternative to ...

Hi Scott, This particular error: java.lang.SecurityException: JAR manifest application-library-allowable-codebase mismatch for http://www.mbepapers.org:8080/editor-1/ ... APSHOT.jar would mean that in the main applet JAR library in the Manifest.mf the application-library-allowable-codebase property ...

Hi, So you have a DITA OT 2.0 distribution in which you integrated the Oxygen XML WebHelp plugin, right? Did you integrate the latest Oxygen XML WebHelp plugin (the one which was released along with Oxygen 17.0)? Because it is the only WebHelp plugin which should work with both DITA OT 1.8 and 2.0 (...

Hi Carole, So how exactly did you mark the bookmap? Did you set the @otherprops attribute on the root element or on the title? You should have use instead the @outputclass attribute because profiling attributes, like @otherprops usually get removed in the filtering stage. And in the XSLT you could h...

Hi Dan,

Thanks for the report, we know about this limitation and we'll update this forum thread when the issue gets fixed.

Regards,
Radu

Hi Doug, No problem, I think XQuery is similar to XSLT in this behavior. When you copy entire chunks of XML content from the original document to the output the namespace declarations in the original document get copied to the output. But when in the XQuery or XSLT you run an XPath you need to decla...

Hi, Yes, I also think that renaming resources (topics or images or whatever) in the Project view should trigger updates in other XML documents if Oxygen knows the ways in which each XML document can link to various resources. We'll try at some point to improve on this and I will update the thread wh...

Hi Doug, We do not work very much with XQuery ourselves. So ideally you could try to find a specialized users list for this. Why don't you declare the xlink prefix at the beginning of the XQuery file? Like: xquery version "3.0"; declare default element namespace "http://docbook.org/ns...

Hi,

Nice catch, we managed to reproduce the issue on our side and hopefully we'll have a fix for it in one of the Oxygen minor bug fix releases. We'll update this thread when we do. Sorry for the inconvenience.

Regards,
Radu

Hi Doug, Indeed in the Java 1.8 runtime libraries there is a java.util.Base64 , I was testing with Java 1.7. The reason this construct encoder:encodeToString does not work is that the method encodeToString is not static. You would need to call in the XQuery code the equivalent of: java.util.Base64.g...