Overview

The Custom tab declares a Pre content and Post content user customisation for a tag or custom marker mapping. As the names imply, the pre-content customisation is processed immediately before the content of the tag being mapped and the post-content customisation is processed immediately after the tag being mapped.

Each user customisation contains a mixture of the following:

  • Text — rendered in the output as if it had been keyed into the input at that point (see “Examples”).

  • Commands — resemble XML tags but always begin with a lower case letter: <space width="9pt"/>. Commands provide access to additional typesetting functions not directly available from the standard mapping dialogs (see “Commands”).

  • Custom Markers — resemble tags but always begin with an upper case letter: <RunHead type="normal"/>. They are defined by the user to supplement the markup supplied by the input document (see “Custom markers”).

  • Variables — identify references to stored content, strings, or values defined by either the user or the system (see “Variables”). Variables are referenced by enclosing the variable name within a { and } bracket pair (for example, {VarName}). Variables may be freely intermixed with text, commands, custom markers or within attribute values.

Some mappings have no content, while others have their content suppressed by setting Suppress element content in the Content tab (see General group”). Commands and custom markers must start and end within the same customisation (except where the <tag/> notation is used to combine them) — you cannot, for example, start a command in a pre-content customisation and finish it in a post-content customisation.

[Warning] Warning

Document tags can not be referenced directly within custom content. The construction <abc/> in a customisation represents a command, while <Abc/> is a custom marker. You may however define a custom mapping that is identical to the mapping of some tag in the document.