>>48 It is not the e, it is two bytes before it. Someone somehow managed to insert an invalid unicode sequence (0085). Twice. The easiest fix would be to delete messages 190 and 191. That won't prevent it from happening again, though.