|
|||||
|
|
|||||
| Markup processing rules | |||||
| Prerequisite Concepts | |||||
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, and are as follows:
data-content rules, allowing you to capture the parsed character data content of elements.
document-end rules, 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, meaning that they're useful for doing process cleanup and final processing before a program completes.
document-start rules, fired just before the implicit parsing of an SGML or XML document begins. document-start rules are "initialization" rules, making them useful 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, used in programs that process marked-up documents that contain a DTD. dtd-end rules are fired after the DTD has been completely processed.
dtd-start rules, fired after the doctype element has been specified in a DTD, but before the main part of the DTD is processed.
element rules, used to execute specified actions when the element named in the element rule 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, used in programs that process marked-up documents that contain a document epilog. epilog-start rules fire just before the processing of the document epilog begins.
external-data-entity rules, 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, used to provide the full-text replacement for each external text entity that appears in the input document.
invalid-data rules, used in processing SGML and XML documents and give you control over how erroneous data appearing in the input document is processed.
marked-section rules, provided so that you can 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, fired whenever a markup comment is encountered in an input document and allow you to control how the content of the comment is processed.
markup-error rules, fired if an error is encountered in the markup of an input document.
processing-instruction rules, giving you control over how processing instructions that are encountered in SGML and XML documents are processed.
prolog-end rules, used in programs that process marked-up documents that include a document prolog. prolog-end rules are fired just after the prolog has been completely processed.
prolog-in-error rules, fired if an error is encountered in the prolog of a marked-up input document.
sgml-declaration-end rules, 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, fired when data content matching a specified pattern occurs within an element of an SGML or XML input document.
|
Prerequisite Concepts Markup languages |
| ---- |
