Theo Van Dinter <[EMAIL PROTECTED]> writes:
> Specifically, in PerMsgStatus::get_decoded_body_text_array(), which 2.6x
> uses to get the uri list from, the un-quoted-printable code is:
>
> s/\=3D([0-9A-F]{2})/chr(hex($1))/ge;
Quoted-printable does not allow lowercase letters, so [0-9A-F] is
technically correct (RFC 2045). However, decoding lowercase seems to be
permitted if the data is definitively quoted-printable (that is, QP is the
Content-Transfer-Encoding or there is a "?Q?" specifier on the header).
I think this is exactly what we do right now, so no problem. We might
want to double check some common MUAs to make sure they do actually decode
lowercase hex, though.
One thing I think you said did give me pause. I'm pretty sure that:
(in a quoted-printable part)
http://penistone=3D2eopoloveok=3D2ecom/3/
should only decode to
http://penistone=2eopoloveok=2ecom/3/
No more than that.
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
