Rather than always failing silently, file translation
code should present warnings at various levels of
verbosity on errors.
Possible levels:
- Silent (for embedded/GUI code)
- Minimal (for default command-line translation)
e.g. file position for errors, one to two lines of
output
- Debugging (giving particular methods, filenames, etc.)
Logged In: YES
user_id=21420
The new OBMessageHandler class in the CVS code takes care of much of
this. The format code (and others) need to take advantage of the new
class more, but support exists to solve this PR.