Special field for setting the transtype for DITA transform scenarios?
I have created a custom XHTML transformation type as a Toolkit plugin. In poking around the DITA transformation scenario dialog there doesn't appear to be a direct way to specify what becomes the -Dtranstype={transtype} parameter in the Java command that runs Ant. I realize I can set the parameter in the Advanced tab or use the effective ant target in the Build target field, but I think it would be helpful to have a dedicated field for custom trans types. Or have I missed something in the UI? Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com
Hello Eliot, We divided the DITA scenarios by "type" because we wanted to propose the applicable parameters for each type in the Parameters list. In the Parameters tab you can just add "transtype" with the desired value. Setting the "transtype" in the Parameters should override the default scenario type (XHTML, PDF, etc). Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Eliot Kimber wrote:
I have created a custom XHTML transformation type as a Toolkit plugin. In poking around the DITA transformation scenario dialog there doesn't appear to be a direct way to specify what becomes the -Dtranstype={transtype} parameter in the Java command that runs Ant.
I realize I can set the parameter in the Advanced tab or use the effective ant target in the Build target field, but I think it would be helpful to have a dedicated field for custom trans types.
Or have I missed something in the UI?
Cheers,
E.
On 12/2/09 12:53 AM, "Radu Coravu" <radu_coravu@sync.ro> wrote:
Hello Eliot,
We divided the DITA scenarios by "type" because we wanted to propose the applicable parameters for each type in the Parameters list. In the Parameters tab you can just add "transtype" with the desired value. Setting the "transtype" in the Parameters should override the default scenario type (XHTML, PDF, etc).
OK. In my case, I've created a new trans type that is effectively an extension of the base XHTML trans type, so it still makes sense to use the XHTML parameters as a base. I think this is a reasonably common case as there are so many outputs that build off the XHTML base. Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com
Hi Eliot, We'll think of a solution to change the "transtype" more easily for a scenario. Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Eliot Kimber wrote:
On 12/2/09 12:53 AM, "Radu Coravu" <radu_coravu@sync.ro> wrote:
Hello Eliot,
We divided the DITA scenarios by "type" because we wanted to propose the applicable parameters for each type in the Parameters list. In the Parameters tab you can just add "transtype" with the desired value. Setting the "transtype" in the Parameters should override the default scenario type (XHTML, PDF, etc).
OK. In my case, I've created a new trans type that is effectively an extension of the base XHTML trans type, so it still makes sense to use the XHTML parameters as a base. I think this is a reasonably common case as there are so many outputs that build off the XHTML base.
Cheers,
E.
participants (2)
-
Eliot Kimber -
Radu Coravu