Interactions during customized transformation
The interaction among various files to obtain customized output still begins with the Generate Output dialog.
Consider a typical transformation scenario that adds a few options to the default
Dita2Pdf
output type after you rename it to AcmePdf.
To customize a transformation scenario, follow the procedure in Customize an existing transformation scenario.
The following summary reflects the flow of interactions.
- You must add a new output type. Follow the process at Add a custom output type.
The output type for
AcmePdf
is defined in <outgen>/conf/client/outputtypes.xml and points to the preprocessor namedAcmePdf
. The output nameAcmePdf
is what the user sees in the Generate Output dialog for an output type.Note: To avoid exposing system default output types to your users, edit the access rights for the output type names to only include roles and groups who can view and use that output type. See Output access rights.If you do use access rights as described, always leave the System Administrator group for the following: Dita2Pdf, Dita2Html, Export, and Export (DRM). - You must add a new preprocessor. Follow the process at Add a custom preprocessor.
The custom preprocessor named
AcmePdf
is defined in <outgen>/conf/client/preprocessors.xml. It defines the conductor file using the value of parameter namebuildfile
and the target within the conductor using value of the parameter nametarget
. - You must add a new conductor target. Your entry will point to and build the
pdf2
transformation type supplied by the plugin you installed and integrated into DITA-OT. After reading Conductor or build files, follow the process at Create a custom transformation target.