Add and configure output types
You add and configure output types in the Outputs tab of the Build Manifest window.
For each output type, you define the following information in the Output type
information area:
- Type: Name of the output type from the Output
Generator. Note: You need to be connected to a running Output Generator before you can define output types. The Build Manifest feature retrieves the list of available output types from the running Output Generator.
- Status: Specifies whether the output type is enabled or not. This can be useful if you want to configure an output type without generating it right away. When set to DISABLED, the output type will not be generated when you output the Build Manifest.
- Description: Description of the output type.
You can also override the following values for the output type:
- Ditaval: Ditaval file that will be used for this output type. If you specify a ditaval file for the output type, the default ditaval file specified in the Default values tab (if any) will be ignored.
- Languages: Languages that will be used for this output type. If you specify a language for the output type, the default language(s) specified in the Default values tab (if any) will be ignored.
- User parameters: User parameters that will be used for this output
type. These are the user parameters that are defined in the transformation
scenario for the output type. If you specify parameters for the output type,
the default parameters specified in the Default
values tab (if any) will be ignored. The name specified in
the Key must match *exactly* the name of the user parameter as defined in
the preprocessors.xml file of the Output
Generator.Important: User parameters are not cumulative. For example, if you set parameter values at the Default level and then set other parameter values at the Output type levels, only the parameters set at the Output type level will be used.
The following diagram shows the Output type tab for the CMS User Guide. Six output types are created for this document:
- 2 Dita2PDF (one oXygen and one XMetaL)
- 2 Dita2xhtml (one oXygen and one XMetaL)
- 2 Dita2EclipseHelp (one oXygen and one XMetaL)
This is necessary since the oXygen and XMetaL versions require different ditaval files and user parameters.
The final step is to output the Build Manifest.