Declaration condition conflict.
#2011 Compile-time error
Declaration condition conflict.
Additional Information
An unconditional INSERTION-BREAK declaration has already been
entered, so no further INSERTION-BREAK declarations are allowed for it.
or
The current INSERTION-BREAK declaration must have a condition, since
the previous INSERTION-BREAK declarations also have conditions.
or
An unconditional REPLACEMENT-BREAK declaration for 'X' has already been
entered, so no such further declarations are allowed for it.
or
The current REPLACEMENT-BREAK declaration for 'X' must have a
condition, since the previous such declarations also have conditions.
Recovery
Compilation continues but no compiled source code file will be saved.
Explanation
If there is more than one insertion-break declaration in a
program, at most one declaration may be applicable at any one time.
Similarly, if OmniMark attempts to replace a single character with
a string from a replacement-break declarations, it verifies that
at most one such rule is applicable at any one time. If a declaration
for insertion or character replacement has no condition, it is always
true, and there is no need to enter any other declarations for that
particular type.