9.3 Publishing ConTeXt documents

This publishing style is capable of producing ConTeXt or PDF documents.

If you wish to publish PDF documents based on ConTeXt, you will need to have it installed. For Debian and Ubuntu, this can be accomplished by installing the “texlive” package.

Styles provided

context

Publish a ConTeXt document.

context-pdf

Publish a PDF document, using an external ConTeXt document conversion tool.

context-slides

Produce slides from a ConTeXt document.

Here is an example of a slide.

          * First Slide
          
          [[Some-sort-of-cute-image.png]]
          
          ** A subheading
          
           - A bullet point.
           - Another bullet point.
          
          * Second Slide
          
          ... and so on

context-slides-pdf

Publish a PDF document of ConTeXt slides.

Options provided

muse-context-extension

Default file extension for publishing ConTeXt files.

muse-context-pdf-extension

Default file extension for publishing ConTeXt files to PDF.

muse-context-pdf-program

The program that is called to generate PDF content from ConTeXt content.

muse-context-pdf-cruft

Extensions of files to remove after generating PDF output successfully.

muse-context-header

Header used for publishing ConTeXt files.

This may be text or a filename.

muse-context-footer

Footer used for publishing ConTeXt files.

This may be text or a filename.

muse-context-markup-regexps

List of markup regexps for identifying regions in a Muse page.

For more on the structure of this list, See muse-publish-markup-regexps.

muse-context-markup-functions

An alist of style types to custom functions for that kind of text.

For more on the structure of this list, See muse-publish-markup-functions.

muse-context-markup-strings

Strings used for marking up text.

These cover the most basic kinds of markup, the handling of which differs little between the various styles.

muse-context-slides-header

Header for publishing a presentation (slides) using ConTeXt.

Any of the predefined modules, which are available in the tex/context/base directory, can be used by writing a "module" directive at the top of the Muse file; if no such directive is provided, module pre-01 is used. Alternatively, you can use your own style ("mystyle", in this example) by replacing "\usemodule[]" with "\input mystyle".

This may be text or a filename.

muse-context-slides-markup-strings

Strings used for marking up text in ConTeXt slides.

muse-context-markup-specials-document

A table of characters which must be represented specially. These are applied to the entire document, sans already-escaped regions.

muse-context-markup-specials-example

A table of characters which must be represented specially. These are applied to example> regions.

With the default interpretation of <example> regions, no specials need to be escaped.

muse-context-markup-specials-literal

A table of characters which must be represented specially. This applies to =monospaced text= and <code> regions.

muse-context-markup-specials-url

A table of characters which must be represented specially. These are applied to URLs.

muse-context-markup-specials-image

A table of characters which must be represented specially. These are applied to image filenames.

muse-context-permit-contents-tag

If nil, ignore <contents> tags. Otherwise, insert table of contents.

Most of the time, it is best to have a table of contents on the first page, with a new page immediately following. To make this work with documents published in both HTML and ConTeXt, we need to ignore the <contents> tag.

If you don't agree with this, then set this option to non-nil, and it will do what you expect.