The Custom tab declares a Pre content and Post content user defined customisation for a tag or custom marker mapping. As the names imply, the content of these fields is processed immediately before and after the content of the tag being mapped. Each field contains a mixture of the following:

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

  • Commands — resemble XML/SGML tags but always begin with a lower case letter: <space width="9pt"/>. Allow the user to access internal system functions not available in 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 — of the form {VarName} which are named strings, defined either by the user or the system (see “Variables”). Variables may be freely intermixed with text, between markers or within attribute values.

Some mappings have no content, while others have their content suppressed by clicking Suppress element content in the Content tab (see General group”). In this case the Pre content and Post content customisations are processed as a single set of actions. Each start tag of a command or custom marker must have a corresponding end tag within the same customisation (except where the <tag/> notation is used to combine them). This means, for example, that you cannot start a command in a Pre content customisation and finish it in a Post content customisation.

[Warning] Warning

You may not reference document tag mappings 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.