An up-translation is a translation whose output is generally a complete XML or SGML document. OmniMark parses the XML/SGML document as it is generated, and any errors are reported. The same XML/SGML document that is parsed is the "main output" of the program. Up-translations work well for relatively simple documents. For complex documents, context-translations are almost always preferable.
OmniMark also provides the ability to send information to the main output or the XML/SGML parser individually. This allows you to send the XML/SGML prolog to the XML/SGML parser without sending it to the main output, for example. That way, the output consists solely of the document instance. This is very useful for environments where the document instances are stored separately from the DTDs.
An up-translation must begin with
up-translate.OmniMark places no restrictions on the format of the input to an up-translation.
When writing an up-translation, use
find rules to describe the patterns of interest in a document and the actions to take to transform the document into an XML/SGML document.
An up-translation operates as follows:
As markup is found and submitted to the parser, OmniMark will collect context information; that is, it will collect information about the document hierarchy being formed. This context information can be used in
find rules to qualify subsequent
In an up-translation, the XML/SGML document created is strictly a result of the patterns that can be found, in context, in the input document. The final XML/SGML document provided at the output is identical to the document provided to the parser.
If there are errors in the generated markup, the parser will report the markup errors and perform as much error correction as possible. You can customize or even act upon error reports to help the program recover from such markup errors.