[Python-bugs-list] [ python-Bugs-463996 ] quopri RFC 2047 and hex 20 encodings

[noreply@sourceforge.net]

Bugs item #463996, was opened at 2001-09-22 19:34
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=463996&group_id=5470

Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Barry Warsaw (bwarsaw)
Assigned to: Nobody/Anonymous (nobody)
Summary: quopri RFC 2047 and hex 20 encodings

Initial Comment:
In RFC 2047, the quoted-printable (i.e. "Q") encoding
allows for _ to encode hex 20.  See section 4.2 of that
RFC.  However, quopri was written against RFC 1521
which doesn't describe hex20/underscore encoding.

quopri should be updated to allow for decoding of
underscore to hex 20, perhaps as a flag on the decode()
and decodestring() functions.

----------------------------------------------------------------------

Comment By: Kent Engström (kente)
Date: 2001-09-23 07:04

Message:
Logged In: YES 
user_id=178855

See patch 464070 for a minimal decode enhancement.


----------------------------------------------------------------------

Comment By: Kent Engström (kente)
Date: 2001-09-23 04:24

Message:
Logged In: YES 
user_id=178855

We should not directly compare RFC 2047 and RFC 1521.

RFC 1521 = Old standard, "QP for bodies"
RFC 1522 = Old standard, "QP for headers"

RFC 2045 = New standard, "QP for bodies"
RFC 2027 = New standard, "QP for headers"

The "underscore coding" is present already in RFC 1522,
and absent in RFC 2045.

A flag sent to the relevant functions may be the right way, but we want it to be something like "header_style", not "new_style".


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=463996&group_id=5470