Advertisement
• The settings in the DITA initialization file (ditafm.ini), which determine the Apache Ant file to be
used for different target outputs.
• Apache Ant scripts, in general, and their role in defining publishing processes that generate
output from the DITA Open Toolkit.
• The XSLT style sheets that are used to generate HTML and other forms of output with the
DITA Open Toolkit, as well as the other files that control the format of output, such as
cascading style sheets.
Using the Selected Target option
A user can customize using the selected target option. The ditafm.ini file provides users with entry
points from where they can run various Ant scripts. Also, for customizing Ant scripts, the user also
needs to have a basic understanding of these scripts.
When you use the Selected Target option, rather than starting an Ant script that is preset to process
the currently open file, you start an Ant script without parameters. The Ant script must contain
explicit instructions about the following:
• Files to process
• Folders to be used for different forms of output
• Publishing methods and processes
While the Selected Target option requires more setup than the Current File option, it offers more
fine-grained control.
About Ant scripts
Apache Ant, a Java™ application installed with the DITA Open Toolkit, is used for automating soft-
ware build processes. For example, the following types of publishing processes can be automated:
1 Transform specified XML files, such as DITA map files or associated topic files, with XSLT style
sheets, to generate XHTML output.
2 Run a subsequent process to place these files into specific folders for deployment to a website.
With Ant, such processes are completely controlled by an Ant script or XML build file, which
defines the following:
• All steps of the publishing process, including the processes or applications called, the target and
destination folders and files
• Processing sequence
Example custom Ant script
If the DITA Open Toolkit is properly installed, you should see a file named PROJECT.xml in your
DITA_OT folder, such as C:\dita-ot1.2.\PROJECT.xml. You can define any custom publishing pro-
cesses by copying, renaming, and modifying the PROJECT.xml file. In addition, you must modify
the DITA initialization file.
For example, to process DITA files located in the C:\Projects\Test folder, do the following:
1 Create a folder named C:\Projects\Test and copy all .dita and .xml files from the source folder to it.
Source refers to the location where you extracted the OpenToolkit.zip file. See Appendix 2 for
details.
2 Copy PROJECT.xml to your Open Toolkit (typically, C:\dita-ot1.4.2.1) folder and rename
PROJECT.xml to Test.xml.
3 Open Test.xml in Windows® Notepad® (Start > Programs > Accessories > Notepad). In steps 4
through 9, you will set the main properties indicated in the comments, which appear at the begin-
ning of the file.
Using the Open Toolkit plug-in for FrameMaker
4
Advertisement
