[brailleblaster] Log levels, mapping mismatch
- From: "Michael Whapples" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "mwhapples@xxxxxxx" for DMARC)
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Tue, 15 Jul 2014 18:01:35 +0100
Hello,
The liblouis/liblouisutdml logging API and the BrailleBlaster logger
have different levels and so do not quite match up properly.
Here are the levels for liblouis/liblouisutdml: FATAL, ERROR, WARN, INFO
and DEBUG. Here are the levels in BrailleBlaster: SEVERE, WARNING, INFO,
CONFIGURATION, FINE, FINER and FINEST.
We only need to go from the liblouis/liblouisutdml levels to the
BrailleBlaster ones, we do not need to go the other way.
In mapping these I felt may be i should make INFO and WARNING levels on
both match each other. The issue then is that liblouis/liblouisutdml has
an additional higher priority level.
I resolved this mismatch by mapping both FATAL and ERROR to SEVERE.
How do others feel? Should I have mapped ERROR to WARNING? Another
option would to have not mapped INFO to INFO and WARN to WARNING and
just mapped each at increasing levels (eg. FATAL-SEVERE, ERROR-WARNING,
WARN-INFO, INFO-CONFIGURATION, DEBUG-FINE).
Michael Whapples
Other related posts:
