Difference: PdfPlugin ( vs. 1)

Typical Use Cases

• Huge printouts, which need table of contents with page numbers
• Nice printouts with running headers, logos, properly scaled images
• Nice presentations with controlled page breaks, automatic sequence etc.
• Online Manuals in one file with hierarchic navigation

How to write

Book-mode

large document with <h1> chapter headings; adds title page + table of contents page(s)

Article-mode

if no chapter headings are present, render just a small title header on the first page.

Syntax Rules

Authors

Users have to care only, if they need hand-made presentation markup. Then use the HTML comments understood by the HTMLDOC tool -- see section 4 'tbd' of the manual.

Examples

You have a simple page without <h1> headline: the plugin creates a simple PDF. Then:

• The page title (its WikiWord) is inserted as =<h1> headline at the beginning of the text.

You have a large document -- typically with a lot of includes -- and supplied a =<h1> headline. Then:

• The text section leading up to that first headline is taken as abstract.
• An extra title page template is loaded, e.g. pdftitle.tmpl.
• The abstract and the aforementioned fields are filled in. (The native %REVINFO% doesn't cut it for a nice printout.)
• A table of contents begins on the next sheet.
• The text body begins on the next sheet.

PdfPlugin Global Settings

Plugin settings are stored as preferences variables. To reference a plugin setting write %<plugin>_<setting>%, i.e. %INTERWIKIPLUGIN_SHORTDESCRIPTION%

• One line description, is shown in the TextFormattingRules topic:
  • Set SHORTDESCRIPTION = Use HTMLDOC to postprocess your page into PDF

• Debug plugin: (See output in data/debug.txt)
  • Set DEBUG = 0

• My own setting: Check the templates directory

Administration

<-- versions below in reverse order -->