Fix exception thrown when seeing a log that contains non-ascii chars.

Having to deal with non-ascii characters in log files is a corner case I suppose - yet I need it :-(