A.3. Producing Formatted Output
Prev | Appendix A. Examples |

## A.3. Producing Formatted Output

This section assumes that you have installed the software listed in the `textproc/docproj` port, either by hand, or by using the port. Further, it is assumed that your software is installed in subdirectories under `/usr/local/`, and the directory where binaries have been installed is in your `PATH`. Adjust the paths as necessary for your system.

### A.3.1. Using Jade

Example A.3. Converting DocBook to HTML (One Large File)
`%` `jade -V nochunks \ -c /usr/local/share/xml/docbook/dsssl/modular/catalog \ -c /usr/local/share/xml/docbook/catalog \ -c /usr/local/share/xml/jade/catalog \ -d /usr/local/share/xml/docbook/dsssl/modular/html/docbook.dsl \ -t sgml `file`.xml > `file`.html`

| Specifies the `nochunks` parameter to the stylesheets, forcing all output to be written to the standard output (using Norm Walsh's stylesheets).
| Specifies the catalogs that Jade will need to process. Three catalogs are required. The first is a catalog that contains information about the DSSSL stylesheets. The second contains information about the DocBook DTD. The third contains information specific to Jade.
| Specifies the full path to the DSSSL stylesheet that Jade will use when processing the document.
| Instructs Jade to perform a transformation from one DTD to another. In this case, the input is being transformed from the DocBook DTD to the HTML DTD.
| Specifies the file that Jade should process, and redirects output to the specified `.html` file.

Example A.4. Converting DocBook to HTML (Several Small Files)
`%` `jade \ -c /usr/local/share/xml/docbook/dsssl/modular/catalog \ -c /usr/local/share/xml/docbook/catalog \ -c /usr/local/share/xml/jade/catalog \ -d /usr/local/share/xml/docbook/dsssl/modular/html/docbook.dsl \ -t sgml `file`.xml`

| Specifies the catalogs that Jade will need to process. Three catalogs are required. The first is a catalog that contains information about the DSSSL stylesheets. The second contains information about the DocBook DTD. The third contains information specific to Jade.
| Specifies the full path to the DSSSL stylesheet that Jade will use when processing the document.
| Instructs Jade to perform a transformation from one DTD to another. In this case, the input is being transformed from the DocBook DTD to the HTML DTD.
| Specifies the file that Jade should process. The stylesheets determine how the individual HTML files will be named, and the name of the “root” file (i.e., the one that contains the start of the document.

This example may still only generate one HTML file, depending on the structure of the document you are processing, and the stylesheet's rules for splitting output.

Example A.5. Converting DocBook to Postscript

The source XML file must be converted to a TeX file.

`%` `jade -V tex-backend \ -c /usr/local/share/xml/docbook/dsssl/modular/catalog \ -c /usr/local/share/xml/docbook/catalog \ -c /usr/local/share/xml/jade/catalog \ -d /usr/local/share/xml/docbook/dsssl/modular/print/docbook.dsl \ -t tex `file`.xml`

| Customizes the stylesheets to use various options specific to producing output for TeX.
| Specifies the catalogs that Jade will need to process. Three catalogs are required. The first is a catalog that contains information about the DSSSL stylesheets. The second contains information about the DocBook DTD. The third contains information specific to Jade.
| Specifies the full path to the DSSSL stylesheet that Jade will use when processing the document.
| Instructs Jade to convert the output to TeX.

The generated `.tex` file must now be run through `tex`, specifying the `&jadetex` macro package.

`%` `tex "&jadetex" `file`.tex`

You have to run `tex` at least three times. The first run processes the document, and determines areas of the document which are referenced from other parts of the document, for use in indexing, and so on.

Do not be alarmed if you see warning messages such as LaTeX Warning: Reference `136' on page 5 undefined on input line 728. at this point.

The second run reprocesses the document now that certain pieces of information are known (such as the document's page length). This allows index entries and other cross-references to be fixed up.

The third pass performs any final cleanup necessary.

The output from this stage will be ``file`.dvi`.

Finally, run `dvips` to convert the `.dvi` file to Postscript.

`%` `dvips -o `file`.ps `file.dvi``
Example A.6. Converting DocBook to PDF

The first part of this process is identical to that when converting DocBook to Postscript, using the same `jade` command line (Example A.5, “Converting DocBook to Postscript”).

When the `.tex` file has been generated you run pdfTeX. However, use the `&pdfjadetex` macro package instead.

`%` `pdftex "&pdfjadetex" `file`.tex`

Again, run this command three times.

This will generate ``file`.pdf`, which does not need to be processed any further.

Prev | Up |
A.2. DocBook `article` | Home |

All FreeBSD documents are available for download at http://ftp.FreeBSD.org/pub/FreeBSD/doc/

Questions that are not answered by the documentation may be sent to <freebsd-questions@FreeBSD.org>.
Send questions about this document to <freebsd-doc@FreeBSD.org>.