start.cmd integrated with oXygen

[susannecm]

I am trying to convert a Word document to DITA using the OT integrated with oXygen und the DITA4Publishers plugin. Since I dont't know how to set up a transformation scenario for this, for a start, I'm trying to call the plugin via the command line. The start.cmd file in the oXygen directory sets ANT_HOME to the directory where Ant can be found in an independent DITA OT installation. Just thought I let you know.

Susanne

[Radu]

Hi Susanne,

What we usually do with the bundled DITA OT is to take an independent DITA OT installation and strip from it the libraries and tools which already exist in Oxygen. So yes, if you want to run the command line you should set the ANT_HOME in the "startcmd.bat" to point to OXYGEN_INSTALLATION_DIR\tools\ant\. We did not modify it ourselves because most of the times users use our GUI to run ANT scenarios.

From what I've experienced with the D4P, I think the easiest way to run the conversion would be this:
Open the DOCX file in Oxygen (it should open in the Archive Browser), open from it the "document.xml".
Press the Configure Transformation Scenario toolbar button.
If you are using Oxygen 14.1 you should already have a transformation scenario there called DOCX DITA. If not you can create a scenario of type ANT points to the build file:

${frameworksDir}/dita/DITA-OT/plugins/net.sourceforge.dita4publishers.word2dita/build-word2dita.xml

If you have trouble with this, just email us (support@oxygenxml.com) and I can give you an export of such a transformation scenario.

Regards,
Radu

[susannecm]

Hi Radu,

I do have oXygen 14.1 and found the transformation. It worked straight away, so easy .

Before that, I had already made more attempts to fix start.cmd. But this does not only require to modify Ant home, Saxon is also somewhere else, and then you need a different version of Saxon. This gets quite cumbersome, it's probably easier to start from scratch. Which is similar to what the oXygen manual actually recommends (http://www.oxygenxml.com/doc/ug-editor/ ... -line.html) - of course I found that even later. Maybe you could just remove these start scripts entirely from the distribution.

Did I mention that I really like to work with your product, and support quality is top notch?

Best regards

Susanne

[Radu]

Hi Susanne,

I do have oXygen 14.1 and found the transformation. It worked straight away, so easy .

Actually we have plans to integrate the D4P plugins directly in the DITA OT which comes with an Oxygen installation. We are just waiting for the next stable version of the D4P plugins.

Before that, I had already made more attempts to fix start.cmd. But this does not only require to modify Ant home, Saxon is also somewhere else, and then you need a different version of Saxon. This gets quite cumbersome, it's probably easier to start from scratch. Which is similar to what the oXygen manual actually recommends (http://www.oxygenxml.com/doc/ug-editor/ ... -line.html) - of course I found that even later. Maybe you could just remove these start scripts entirely from the distribution.

Indeed, we remove the Saxon libraries which come with DITA OT we use our own Saxon Enterprise Edition libraries. Sorry I did not previously give you that link to our DITA OT command line help topic.
We'll consider removing the scripts from the bundled DITA OT.

Regards,
Radu