OmniMark provides a complete set of markup rules that can be used to process documents that have been marked up with SGML- or XML-based markup languages. These rules correspond to all the features of SGML and XML.

data-content rules allow you to capture the parsed character data content of elements.

document-end rules are fired immediately after the parsing of an SGML or XML document has been completed in an aided translation type program. document-end rules are termination rules: they can be used for doing process cleanup and final processing before a program completes.

document-start rules are fired just before the implicit parsing of an SGML or XML document begins. document-start rules are initialization rules: they can be used for doing any sort of program setup that has to be done before the main processing begins. These rules can only be used in aided translation type programs.

dtd-end rules can be used in programs that process marked-up documents containing a DTD. dtd-end rules are fired after the DTD has been completely processed.

dtd-start rules are fired after the doctype element has been specified in a DTD, but before the main part of the DTD is processed.

element rules are used to execute specified actions when the element named in the element rule header is encountered in the input document. It is important to note that each element that appears in an SGML or XML document must be uniquely accounted for in an OmniMark program. You must have an element rule that can be fired for each individual occurrence of every element in a document.

epilog-start rules fire just before the processing of the document epilog begins.

external-data-entity rules can be used to specify special processing of external data entities that are encountered in SGML or XML documents. Note that you must have an external-data-entity rule that can be fired for each occurrence of an external data entity in a document.

external-text-entity rules can be used to provide the full-text replacement for each external text entity that appears in the input document.

invalid-data rules can be used in processing SGML and XML documents to control the processing of erroneous data appearing in the input document.

marked-section rules provide the ability to specify the processing of any type of marked section that appears in an SGML or XML document. Marked sections types include cdata, rcdata, ignore, and include.

markup-comment rules are fired whenever a markup comment is encountered in an input document; they provide control over how the content of the comment is processed.

markup-error rules are fired if an error is encountered in the markup of an input document.

processing-instruction rules provide control of the handling of processing instructions that are encountered in SGML and XML documents.

prolog-end rules are fired just after the prolog has been completely processed.

prolog-in-error rules are fired if an error is encountered in the prolog of a marked-up input document.

sgml-declaration-end rules can be used in programs that process SGML documents. All SGML documents contain an SGML Declaration, whether it be explicit or implicit, so these rules will always fire if they are used. sgml-declaration-end rules fire after the declaration has been completely processed.

translate rules are fired when data content matching a specified pattern occurs within an element of an SGML or XML input document. translate rules can also be used to process attribute values that are output using %v.

Related Syntax do sgml-parse do xml-parse do markup-parse Xerces XML parser (OMXERCES) Rich Text Format (RTF) (OMRTF) context-translate down-translate up-translate

[ INDEX ] [ CONCEPTS ] [ TASKS ] [ SYNTAX ] [ LIBRARIES ] [ LEGACY LIBRARIES ] [ ERRORS ]