Hi Radu,

Many thanks for your quick reply. We have forked the repo and will probably create our own plugin as a first step. If anything useful comes out of it we will contribute back to the community

Best regards,
Frank

Hi Radu, We want to modify the way review changes are displayed in the PDF output (change bars instead of foot notes). However, we haven't figured out the best way to do this. Is there any extension point? Or can/shall we just override the XSLT in the com.oxygenxml.pdf.review plugin? If we could mak...

Hi, We finally managed to extract version-related metadata from maps and topics by overriding com.oxygenxml.webhelp/xsl/ macroExpander.xsl and defining the following variable: <xsl:variable name="ProductVersion"> <xsl:choose> <xsl:when test="//topicmeta/metadata/prodinfo/vrmlist/vrm&q...

Hi Radu,

That's great! Many thanks for fixing this.

Best regards,
Frank

Hi Radu,

Many thanks for this pointer. Our customer still uses oXygen 17.1 but I will try your suggestion and report back.

Best regards,
Frank

Hi, We deploy an oXygen DITA framework that uses a custom DITA-OT plugin that comes with a .jar library. I know how to add libraries to transformation scenarios but that would require all users to update or re-create their existing transformation scenarios. Is there another way to add and deploy a ....

Just an update regarding the DITAVAL import:

Recent versions of oXygen add *DITA* (with two wildcards) as document type when importing DITAVAL files so above mentioned issue with a document type of "Customer DITA" is solved.

Best regards,
Frank

Hi Alin, The macro mechanism helped indeed with another issue; thanks again. What I want to do is creating release notes in WebHelp output, similar as https://github.com/doctales/org.doctales.release-notes does for PDF output. However, using the following XSLT variable on the top document level is e...

Hi Alin,

Many thanks for this pointer. I wasn't aware of this mechanism. I will give it a try and report back.

Best regards,
Frank

Hi, I'm working on a WebHelp extension to display DITA metadata from the new Release Management domain as visible content. I've already had a look at DITA-OT\plugins\org.dita.xhtml\xsl\xslhtml\ get-meta.xsl and managed to create templates for new metadata elements from the Release Management domain....

Hi Stefan,

Sorry for the late reply. Many thanks for this thorough explanation. I will forward this to our customer.

Best regards,
Frank

Hi, We face the same issue when creating Eclipse help output that we deliver to customers. Black Duck complains about two CSS files ( commonltr.css and commonrtl.css ) from the com.oxygenxml.webhelp plugin that contain the following reference to the Apache license: /* * The Oxygen Webhelp plugin red...

Hi Radu,

Thanks for testing and confirming the issue.

Best regards,
Frank

Hi Adrian,

Thanks for testing and confirming the issue. Your workaround did the trick.

Many thanks for your kind help!
Frank

Hi Adrian,

Thanks for your quick reply. I tried your suggestion but unfortunately it didn't work.

I also had a closer look at the exported global options of oXygen 17.1, 18.1 and 19.1 but none of those files contained any reference to working copies.

Best regards,
Frank

Hi, I'm facing the same problem after upgrading from oXygen 16.1 to 17.1 (the same happened with 18.1 and 19.1): The repository list is taken over to the new version but the working copy list is empty. I tried the above mentioned solution and manually exported the global options from the SVN client ...

Hi Radu, Thanks for your quick reply. I will send you my sample files but they are plain standard DITA. Here's an excerpt: Sample DITA code <ul> <li audience="" product="">1) Only empty attributes. > Included</li> <li audience="invalid" product="">2) audience=...

I had a closer look and the behavior is a bit different but still strange. When setting the default value explicitly to "include" in a DITAVAL file the associated profiling condition in oXygen doesn't work for that attribute.

Frank

Hi, I've noticed a strange behavior when applying profiling condition sets in oXygen that are linked to a DITAVAL file. If I set the default behavior explicitly to "include" for more than one attribute the profiling doesn't seem to work in oXygen anymore. Does not work <val> <prop att=&quo...

Hi Radu,

Thanks for your reply. As with you, we only took one of the existing XML configuration files and added some Matlab-specific keywords. So this can very well be open source. I will contact Jirka Kosek when we are finished.

Best regards,
Frank

Hi Radu, As a follow-up, we have a request for Matlab syntax highlighter . I've already started writing such a highlighter as a proof-of-concept. Should such a highlighter be provided as an addition to the oXygen plugin or better to the original Xslthl library ? I've seen that you are currently work...

Hi Radu,

Many thanks for this pointer and testing.

Best regards,
Frank

Regarding JEuclid, the strange thing is that line breaks do render in the MathML 2.0 test suite but not in the MathML 3.0 test suite.

Hi Radu, Many thanks for your quick reply. Actually, <mspace linebreak='newline' /> should also work with MathML 2.0 . However, most rendering engines don't seem to support line breaking (yet), for example Firefox . But according to http://jeuclid.sourceforge.net/jeuclid-testsuite/svg/testsuite/Pres...

Hi, I've tried both recommended methods to insert a line break in MathML but this is neither rendered in oXygen 16.1 nor in the PDF output when including the MathML in a DITA document. <mspace linebreak='newline' /> <mo linebreak='newline' linebreakstyle='after'>+</mo> Am I missing something? Best r...

Hi Radu,

Many thanks for the pointer.

Best regards,
Frank

Hi Radu, Thanks for your quick response. I need an action where the user can perform a complex find and replace operation with pre-configured regular expression find/replace patterns. The user should not be able to alter the find/replace patterns. Here's an example: Find href="references.dita#[...

Hi,

This request pops up again from time to time. So is this perhaps possible with more recent versions of oxygen?

Best regards,
Frank

Hi Radu,

Thanks for the pointer. We plan to keep DITA-OT 1.8.5 in the first stage of the framework update to focus on the oXygen-related changes (for example, Author Actions) and do the DITA-OT upgrade as a second step.

Best regards,
Frank

Hi Radu,

Actually, we are about to upgrade our framework to oXygen 19.1. So I suppose a lot of old issues will be fixed by that

Best regards,
Frank