4 Messages
Messages about TTH's state and its assessment of the TEX it is
translating are output always to the stderr stream, which
normally displays on the console, but under Un*x type systems can be
redirected to a file if necessary. Normally these messages are one of
three types:
Error Messages
These start **** Error: and indicate some improper condition or
error either in TTH or in the TEX of the file being
translated. Some errors are fatal and cause TTH to stop. On others
it will continue, but the TEX file probably should be corrected in
order to get correct output.
Warnings
These start **** but without reporting Error. They are
messages by which TTH indicates aspects of the translation process
that may not be fully satisfactory, usually because of known limitations,
but which quite likely will not prevent the translated file from
displaying correctly, and so do not necessarily require
intervention. Examples include the use of some dimensions, glue, or similar
TEX commands that have no HTML equivalent.
Informational and external
Lines with no **** are either informational, meaning the state
of the translation is not considered abnormal, or else they may come
from external programs (e.g. makeindex), over which TTH has no
control.
The switch -v causes more verbose messages to be output, which
may be helpful for understanding why errors are reported. A higher
level of verbosity -V can be invoked, but is intended primarily
for internal debugging of TTH and will rarely be comprehensible!
The presumption that lies behind TTH message design is that the file
being translated has been debugged using TEX or LATEX to remove
syntax errors. TTH is not good at understanding or reporting TEX syntax errors and counts only the lines in the main TEX file, not
those in files read by \input. Therefore error reporting by
TTH does not reach even the low standard of clarity set by TEX and
LATEX error messages. Although TEX files can be debugged using
TTH alone, since it is very fast, the process is not recommended for
inexpert TEX users. Moreover, since TTH understands both TEX and
LATEX simultaneously, it can parse some files that TEX or LATEX
separately cannot.