Message316642
| Author |
r.david.murray |
| Recipients |
Jeremy.Hylton, barry, gvanrossum, martin.panter, r.david.murray, serhiy.storchaka |
| Date |
2018年05月15日.11:59:26 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1526385566.11.0.682650639539.issue18022@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I should have just deleted the table, actually.
The only important info in it is that per RFC '=', '=\n', and '= \n' all ought to become '='. But I don't think we should make that change, I think we should continue to turn those into ''. So I consider the (current!) bwehavior of quoprimime to be the correct behavior.
I also gave the example of '= \n foo\n', to show that quopri and binascii aren't stripping trailing blanks, as Martin noted in the other issue. They fold lines if they see '=\n', but not if they see '= \n', which is wrong per the (email!) RFC. I'm not clear if it is wrong for non-email uses of quopric, I haven't tried to research that. |
|