[issue44660] email.feedparser: support RFC 6532 section 3.5

2022-04-01 Thread Francis Johnson
Francis Johnson added the comment: Hello, I haven't had the time to complete @r.david.murrary's recommendation and unfortunately don't anticipate that I will for now. Any objection to me resubmitting the pull request as-is? Alone, it still delivers business value so to speak. Thanks

[issue44660] email.feedparser: support RFC 6532 section 3.5

2021-08-02 Thread Francis Johnson
Francis Johnson added the comment: As requested, I’ve started testing and writing changes for the generator and content manager. I’m assuming there is no rush since the scope is now widened. Will have some follow-on questions about the design

[issue44660] email.feedparser: support RFC 6532 section 3.5

2021-07-23 Thread Francis Johnson
Francis Johnson added the comment: The first paragraph of section 3.5 states two positions that the RFC holds on Content-Transfer-Encodings: (1) “allows newly defined MIME types to permit content-transfer-encoding;” and (2) “allows content-transfer-encoding for message/global (see Section 3.7

[issue44660] email.feedparser: support RFC 6532 section 3.5

2021-07-23 Thread Francis Johnson
Francis Johnson added the comment: Try parsing an example such as this through the Python email library: Content-Type: message/global Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; = charset=3D”us-ascii” Hello, World! You will find that the valid quoted-printable

[issue44660] email.feedparser Module Lacks Support for Section 3.5 of RFC 6532: message/global Emails with non-identity Content-Transfer-Encodings

2021-07-16 Thread Francis Johnson
New submission from Francis Johnson : Note that I have created a fix for this and am working through the Python Developer’s Guide to propose it. -- components: email messages: 397693 nosy: barry, f18a14c09s, r.david.murray priority: normal severity: normal status: open title