Argh. Okay. Perhaps we want to at least mention in the logged parse error the encoding(s) we did try, whichever they may be!