* Christopher J. Madsen wrote: >Dropping support for UTF-32 from HTTP::Message is a separate issue from >removing HTML::Parser. I've got no comment on that.
(It's not quite as black and white as that, "HTML5" could be exempted in the algorithm, for instance.) >> Your UTF-8 validation code seems wrong to me, you consider the sequence >> F0 80 to be incomplete, but it's actually invalid, same for ED 80, see >> the chart in <http://bjoern.hoehrmann.de/utf-8/decoder/dfa/#design>. > >I guess the RE could be improved, but I'm not sure it's worth the effort >and added complication to catch a tiny fraction of false positives. Why make the check at all if you don't care if it's right? >> Anyway, if people think this is the way to go, maybe HTTP::Message can >> adopt the Content-Type header charset extraction tests in HTML::Encoding >> so they don't get lost as my module becomes redundant? > >I thought it already did that? Not as far as I can tell; links welcome though. -- Björn Höhrmann · mailto:bjo...@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
