|
|||||
|
|
|||||
| XML/SGML errors: processing | |||||
| Prerequisite Concepts | Related Syntax | ||||
OmniMark reports three kinds of errors:
OmniMark syntax errors arise from a program that does not conform to OmniMark syntax. These errors are detected before OmniMark attempts to run the program. If any such errors are present, the program is not run.
Some programs do conform to OmniMark syntax, but employ questionable practices that may indicate a coding error. Those situations are reported by warnings. If there are no syntax errors but there are syntax warnings, the OmniMark program will still be run.
Warnings are only reported if the "-warning" command-line switch is specified when OmniMark is run.
OmniMark run-time errors arise from attempting to perform an operation that is not permitted. They cause the immediate termination of the OmniMark program.
Markup errors indicate that the input document does not conform to the markup syntax. When these errors occur in the document instance, OmniMark reports the error, performs the appropriate error recovery, and continues processing.
There can also be markup warnings. Like OmniMark syntax warnings, they are only reported if the command-line option "-warning" is specified.
OmniMark provides additional features to allow the OmniMark programmer to provide customized markup error reporting. These features include:
markup-error rule which is triggered when an SGML or XML error is found by the parser
prolog-in-error rule which can be used by the programmer to gain control before parsing of the current document is terminated because of prolog errors (OmniMark will perform automatic error recovery following markup errors in the document instance, but prolog errors cause OmniMark to abandon parsing of the document.)
|
Prerequisite Concepts Aided translation types Command-line interface Markup languages |
Related Syntax markup-error prolog-in-error sgml-error |
| ---- |
