Revision 941180

added support for 'custom level definitions' in LogFilePatternReceiver, which allows the user to map strings in the log file to Log4j levels
if there are extra spaces that would prevent a pattern from matching, strip them out
exclude empty lines (if appendNonMatches was false, would add an empty line to the log)

With these changes, redirection of Android logging via 'logcat -v time' will now render fine in Chainsaw, using:
<param name="logFormat" value="TIMESTAMP LEVEL/LOGGER(PROP(PID)):MESSAGE"/> 
<param name="customLevelDefinitions" value="V=TRACE,D=DEBUG,I=INFO,W=WARN,E=ERROR,F=FATAL,S=OFF"/>