version 1.215, 2017/07/06 22:59:48 |
version 1.216, 2017/07/07 16:20:30 |
Line 719 so using GNU troff instead of |
|
Line 719 so using GNU troff instead of |
|
.Nm |
.Nm |
to process the file may be preferable. |
to process the file may be preferable. |
.It Cm error |
.It Cm error |
An input file contains invalid syntax that cannot be safely interpreted. |
Indicates a risk of information loss or severe misformatting, |
By discarding part of the input or inserting missing tokens, |
in most cases caused by serious syntax errors. |
the parser is able to continue, and the error does not prevent |
|
generation of formatted output, but typically, preparing that |
|
output involves information loss, broken document structure |
|
or unintended formatting, no matter whether |
|
.Nm |
|
or GNU troff is used. |
|
In many cases, the output of |
|
.Nm |
|
and GNU troff is identical, but in some, |
|
.Nm |
|
is more resilient than GNU troff with respect to malformed input. |
|
.Pp |
|
Non-existent or unreadable input files are also reported on the |
|
.Cm error |
|
level. |
|
In that case, the parser cannot even be started and no output |
|
is produced from those input files. |
|
.It Cm warning |
.It Cm warning |
An input file uses obsolete, discouraged or non-portable syntax. |
Indicates a risk that the information shown or its formatting |
All the same, the meaning of the input is unambiguous and a correct |
may mismatch the author's intent in minor ways. |
rendering can be produced. |
Additionally, syntax errors are classified at least as warnings, |
Documents causing warnings may render poorly when using other |
even if they do not usually cause misformatting. |
formatting tools instead of |
|
.Nm . |
|
.It Cm style |
.It Cm style |
An input file uses dubious or discouraged style. |
An input file uses dubious or discouraged style. |
This is not a complaint about the syntax, and probably neither |
This is not a complaint about the syntax, and probably neither |