[ Main Table Of Contents | Table Of Contents | Keyword Index | Categories | Modules | Applications ]
mpexpand(n) 1.0 tcllib "Documentation toolbox"
mpexpand - Markup processor
This manpage describes a processor / converter for manpages in the doctools format as specified in doctools_fmt. The processor is based upon the package doctools.
- mpexpand ?-module module? format infile|- outfile|-
The processor takes three arguments, namely the code describing which formatting to generate as the output, the file to read the markup from, and the file to write the generated output into. If the infile is "-" the processor will read from stdin. If outfile is "-" the processor will write to stdout.
If the option -module is present its value overrides the internal definition of the module name.
The currently known output formats are
The processor generates *roff output, the standard format for unix manpages.
The processor generates HTML output, for usage in and display by web browsers.
The processor generates TMML output, the Tcl Manpage Markup Language, a derivative of XML.
The processor generates LaTeX output.
The processor generates Wiki markup as understood by wikit.
The processor extracts the information provided by manpage_begin.
The processor does not generate any output.
- mpexpand.all ?-verbose? ?module?
This command uses mpexpand to generate all possible output formats for all manpages in the current directory. The manpages are recognized through the extension ".man". If -verbose is specified the command will list its actions before executing them.
The module information is passed to mpexpand.
Possible future formats are plain text, pdf and postscript.
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category doctools of the Tcllib Trackers. Please also report any ideas for enhancements you may have for either package and/or documentation.
When proposing code changes, please provide unified diffs, i.e the output of diff -u.
Note further that attachments are strongly preferred over inlined patches. Attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar.
expander(n), format(n), formatter(n)
Copyright © 2002 Andreas Kupries <email@example.com>
Copyright © 2003 Andreas Kupries <firstname.lastname@example.org>