Article: The base Wikipublisher document class
When I ask Wikipublisher to typeset a page, what factors determine the presentation style of the PDF output?
In the 16th century, typesetting was a manually intensive task
Wikipublisher uses the PmWiki skins capability to control the look of the printed output. There is a default set of templates, each of which results in output created with a suitable LATEX document class. Wikibook XML is wiki content, generated using a replacement set of markup rules, wrapped in a special skin. The most common class is the article, applied to the typeset versions of individual pages and, optionally, to typeset trails.
By default, the Site.Print Template results in an article with the following properties:
The Wikipublisher article class also supports an optional surtitle. As the name implies, this is printed above the title. This and other document properties can be set using either the options button, a Group.PrintTemplate, or with a (:typeset-page:) directive. For example, this page has a surtitle and a watermark.
PDF settings (show)
An author can also:
In practice, we find that the results produced surpass the quality of the output from most common word processing programs. For the author, this is achieved effortlessly, because Wikipublisher, and its developers, do all the hard work behind the scenes. As always, “God is in the details”.1 Notice — by way of an example — the thin spaces around the em dashes in the PDF, produced automatically.
1 a favorite aphorism of Mies van der Rohe, attributed, without verification, to Gustave Flaubert (Le bon Dieu est dans le détail) (↑)
Category: document type