Hi Peyton,
The DITA OT 2.1 publishing engine only has support for publishing a couple of DITA 1.3 new elements.
Actually you can find here a list of DITA 1.3 improvements, most of them are still opened and only a couple of them have been done until now:
https://github.com/dita-ot/dita-ot/issu ... TA+1.3%22+
Key scopes and branch filtering are also not supported yet by DITA OT 2.1.
Also the DITA OT 2.1 does not come by default with the new DITA 1.3 DTDs. It will probably do this after the DITA 1.3 is officially release, probably next year.
Eliot Kimber made available some DITA 1.3 DTD plugins which can be integrated in DITA OT 1.8 or 2.0:
https://github.com/dita-community/org.o ... 3.doctypes
So these plugins only cover the DITA 1.3-based editing and validation, they do not cover the publishing part.
And, coming back to your original question, yes, you can publish with an external DITA OT 2.1 folder from Oxygen. If you are using the latest Oxygen 17, you just need to edit the transformation scenario and set the "dita.dir" parameter to point to the external DITA OT installation.
If you are using Oxygen 16.1, you need to edit the transformation scenario, go to the "Advanced" tab and click the "Libraries" button. Uncheck the
Allow Oxygen... checkbox. Add another library entry:
${dita.dir.url}/lib/commons-io.jar
and move it to be the first entry in the list. If this does not work, just post the entire output received in the DITA OT console view and I'll look into this.
More about what adding bundled DITA 1.3 support to Oxygen below:
Support for a DITA 1.3 feature needs to have 3 aspects implemented:
1) Use the DITA 1.3 DTDs or schemas when creating topics and maps.
We do not yet ship these with Oxygen, possibly after the DITA 1.3 standard is released we will do this.
2) Oxygen has certain specialized dialogs which can be used to insert for example DITA topicrefs, these dialogs will need to be updated to support the new constraints, new attributes which can be set, etc.
But this is not a showstopper as you can also edit the content in the Text page.
3) The publishing needs to also work with the new features. So the DITA Open Toolkit publishing engine needs to be updated to support new DITA 1.3 features. Some features (like support for new DITA elements like
"strikeout") are quite easy to implement and have already been implemented in DITA Open Toolkit 2.0.
Other features like supports for ditavalref, support for scoped keys are very hard to implement. And we do not have an official timeline from the DITA Open Toolkit developers as to when these will become available.
Regards,
Radu