Hello Martin,
The problem was solved by the Calabash team, and as soon as we release an improved version we will let you know about it.
Regards,
MIrcea.

Hi Greg,

The problem was identified and fixed.
When we will have an official release, we will let you know about it !

Regards,
Mircea.

Hello Frank,

This is good news. Thank you explaining for other users the way you made it work !

Regards,
Mircea

Hi Frank, What is the exact error you obtain after placing the new jar file in the Calabash's lib folder ? There are some possible causes for this: There are some missing dependencies that are required by the PlantUML jar you created. Those jars must be added in the lib folder and in the engine.xml ...

Hello,

We managed to reproduce the problem on a Mac machine.
We will investigate the problem and we'll let you know as soon as we have news about it.

Regards,
Mircea.

Hi Greg,

What are the versions of Eclipse for you and your writer ?

Regards,
Mircea.

Hello, Instead of putting the Oxygen plugins in a custom directory ( /Users/greg/.p2/pool /plugins/com.oxygenxml.editor_24.0.0.v2021101506) try install them using the zip distribution and place the unpacked zips in the dropins folder of your Eclipse installation. Also try to find out what other appl...

Hello, Can you please open for editing in Oxygen the schema placed at "/Users/greg/.p2/pool/plugins/com.oxygenxml.editor_24.0.0.v2021101506/frameworks/dita/resources/dita-1.2-for-xslt2-mandatory.sch" on your computer and check its integrity ? Maybe run a validation ? It seems that somehow ...

Hi,

This is good news !

Regards,
Mircea.

Hello,

That is an error reported by the XProc Calabash engine (https://xmlcalabash.com/) as stated here:
https://spec.xproc.org/master/head/xproc/#err.S0032

For more information we need an actual sample in order to help you.

Regards,
Mircea.

Hello, Using the same kit from our website (both the zip and the "site" distribution we did not managed to reproduce the problem. I think that somehow your installation got corrupted and these 2 files are damaged. Please reconsider re-installing the Eclipse plugin. In case the problem pers...

Hello Boris,

Please consider downloading the 23.1 installation kit that includes the Java SE 8u202.
https://www.oxygenxml.com/xml_editor/do ... ditor.html

Regards,
Mircea.

Hello Martin, You are comparing two different versions of Calabash actually. The one that uses Saxon 9.8.0.8 and the one that uses Saxon 10.2. The calabash itself has the same version ? The last version of Calabash that supports Saxon 9.8 and 10 is 1.2.1. If you are not using the same version of Cal...

Hello, Since all the output is generated through the <xsl:result-document> there is no nedd to fill the "Save As" field. If you need help with the stylesheet please send us some samples files on our support email address (support@oxygenxml.com) and we will try to help you. Regards, Mircea.

Hello Martin, We use the Calabash API in order to provide the XProc transformation support. Basically there is no way to "slow" it down. You can obtain the same result if you configure the Calabash as an external tool. See: https://www.oxygenxml.com/doc/versions/23.1/ug-editor/topics/prefe...

Hello, Maybe you can try to use the <p:for-each> step, that lets you perform a series of steps (a subpipeline) to all of the input documents you provide to it. Unfortunatelly we do not have enough knowledge about this in order to offer you a sollution. I recommend you to address this question on the...

Hello Boris, We tested an XProc transformation using the build file you provided with a local Morgana copy. We cannot reproduce the problem you encountered. This means that we need more complex testing environment from you, i.e. a sample XProc file. Please send it on our email address: support [at] ...

Hello Boris,

You can either configure Morgana as an external tool (from Tools/External Tools, and pass the ${cf} argument which provides the path of the current selected file), or if you create a proper Ant Build file, you can create an Ant Transformation Scenario.

Regards,
Mircea.

Hi Boris, Unfortunatelly we cannot reproduce the problem. We do not have an adaptor that works with Morgana 3. Do you have an Morgana XProc 3.0 adaptor for Oxygen ? Can you point us to it so we can give it a try ? Most probably the problem is from the adaptor, since we only provide an API to be impl...

Hello,

It seems that the place where you are writing the result is not allowing it.
Please check the writing rights on the result paths.

Regards,
Mircea.

Hello, Thank you for the feedback! We implemented this suport for elements only content , as specified by the schema of the document. We cannot detect what is the content of the entity when formatting the document. Having this in mind we decided that putting entities on a different line is acceptabl...

Hello,

Thank you for reporting this issue.
The fix was included in the new 23.1 version that was rele4ased few days ago.

Regards,
Mircea.

Regarding the problem with formatting, we cannot reproduce the same behaviour here.
Please take into consideration to send us a sample on email: support [AT] oxygenxml [DOT] com.
We will analyze it and see if it is a problem.

Hello,

This is a nice feature request, we added it on our issue tracking system.
We will notify you when the new feature is available !

Regards,
Mircea.

Hello Stefan,

The problem you encountered was fixed in the new 23 version of Oxygen that we released last week.

Regards,
Mircea.

Hello Nicholas, I changed the Schematron rule's context like: <sch:rule context="cdf:ElectionReport"> and the XProc transformation works as expected. It seems that the "element(*, $type)" function does not work well when the Schematron is called from an XProc step. We will invest...

Hello,

Can you please give us a small example in order to investigate?

Regards,
Mircea

It seems that we both replyed in the same time.
Yes, the XProc code needs a fix.

It seems that the problem is in the following line: <p:with-option name="href" select="document-uri(.)"/> In my case the "section-X.X.html" files were generated in the oXygen installation directory. It works from the command line because the URI of "." is the ...

I do not have your stylesheet to check the problem.
I used a simple "copy-stylesheet" to check the behaviur, but that do not create additional files.