To build an arbitrary document, use the same method as you would
any other document: make with a specific
-arbitrary after the base name of
the source files indidicates that we should build using the
arbitrary system. For example, to build the Windows arbitrary
document as a PDF, you would use:
Behind the scenes, the following happens:
make executes the arbitrary-parser.pl script. This accepts the arbitrary specification file and template file as arguments.
The script parses and validates arbitrary specification.
For each fragment, the script performs these actions:
includestatement, first loading the file that contains the specified ID.
Extracts the DocBook XML block from the file (be it section, chapter, or appendix).
Removes subsections, if they are filtered.
Updates the appropriate tags, if the section is to be remapped.
includesection has additional subsections defined, these are appended to the end of the section before the closing tag for that section.
When a fragment has been completely generated, the corresponding import specification in the template XML is located and replaced with the fragment text.
The updated template document is written out as a file with name
The generated file is then processed as normal by the rest of the documentation build process into the desired format.