Ability to add custom transformation types (DITA)
Are you missing a feature? Request its implementation here.
-
- Posts: 3
- Joined: Tue Mar 16, 2010 10:37 pm
Ability to add custom transformation types (DITA)
Post by markpeters.work »
Hi,
XML Author 11.2 currently points to my local, customized copy of DITA Open Toolkit 1.5.1. I can output to PDF using the XEP processor. This transformation works fine.
I've added a WordprocessingXML transformation plugin to my team's DITA Open Toolkit. The transformation uses XMLmind XSL-FO Converter to produce the WordprocessingXML output. XML Author doesn't provide the option to add custom transformation types to transformation scenarios. I tried duplicating the default PDF transformation type and adding the "transtype" parameter with the transtype value specified in my build.xml file. XML Author seems to recognize the transtype value -- the log file shows the transtype value. But the tool continues to produce a PDF instead of WordprocessingML output. I presume that the "pdf" transtype value is hardcoded.
Thanks,
Mark
XML Author 11.2 currently points to my local, customized copy of DITA Open Toolkit 1.5.1. I can output to PDF using the XEP processor. This transformation works fine.
I've added a WordprocessingXML transformation plugin to my team's DITA Open Toolkit. The transformation uses XMLmind XSL-FO Converter to produce the WordprocessingXML output. XML Author doesn't provide the option to add custom transformation types to transformation scenarios. I tried duplicating the default PDF transformation type and adding the "transtype" parameter with the transtype value specified in my build.xml file. XML Author seems to recognize the transtype value -- the log file shows the transtype value. But the tool continues to produce a PDF instead of WordprocessingML output. I presume that the "pdf" transtype value is hardcoded.
Thanks,
Mark
-
- Posts: 9473
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Ability to add custom transformation types (DITA)
Hi Mark,
The Oxygen transformation scenarios are, as you noticed, used to create a command line which invokes ANT with your set parameters. You can see the entire invoked command line in the Oxygen console view.
Indeed the transformation types list which appears when editing a DITA Map transformation scenario is hard coded into Oxygen.
But, as you suspected, if you create a PDF scenario for example and add the transtype parameter in the Parameters tab, the transtype value specified in the Parameters tab will take precedence over the hard coded one.
At the end of the transformation Oxygen usually tries to open the output file. The name and extension of the output file is indeed based on the hardcoded transtype of the scenario. If you want to specify another file to open at the end of the transformation in the Scenario Edit dialog there is the Output tab in which you can specify the Other location to open instead of the detected one.
So the best thing to do is to look in the command line executed by Oxygen and see if the transtype is correctly set to it.
If you are still having problems with this one you can send us the entire Oxygen console output to the support@oxygenxml.com support email address.
Regards,
Radu
The Oxygen transformation scenarios are, as you noticed, used to create a command line which invokes ANT with your set parameters. You can see the entire invoked command line in the Oxygen console view.
Indeed the transformation types list which appears when editing a DITA Map transformation scenario is hard coded into Oxygen.
But, as you suspected, if you create a PDF scenario for example and add the transtype parameter in the Parameters tab, the transtype value specified in the Parameters tab will take precedence over the hard coded one.
At the end of the transformation Oxygen usually tries to open the output file. The name and extension of the output file is indeed based on the hardcoded transtype of the scenario. If you want to specify another file to open at the end of the transformation in the Scenario Edit dialog there is the Output tab in which you can specify the Other location to open instead of the detected one.
So the best thing to do is to look in the command line executed by Oxygen and see if the transtype is correctly set to it.
If you are still having problems with this one you can send us the entire Oxygen console output to the support@oxygenxml.com support email address.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service