Message162399
| Author |
mitya57 |
| Recipients |
barry, mitya57, r.david.murray |
| Date |
2012年06月06日.09:13:27 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1338974008.79.0.846609742921.issue15016@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
(Follow-up to issue 14380)
The attached patch makes the email.mime.text.MIMEText constructor use the iso-8859-1 (aka latin-1) encoding for messages where all characters are in range(256). This also makes them use quoted-printable transfer encoding instead of base64.
So, the current algorithm of guessing encoding is as follows:
- all characters are in range(128) -> encoding is us-ascii
- all characters are in range(256) -> encoding is iso-8859-1 (aka latin-1)
- else -> encoding is utf-8 |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年06月06日 09:13:29 | mitya57 | set | recipients:
+ mitya57, barry, r.david.murray |
| 2012年06月06日 09:13:28 | mitya57 | set | messageid: <1338974008.79.0.846609742921.issue15016@psf.upfronthosting.co.za> |
| 2012年06月06日 09:13:28 | mitya57 | link | issue15016 messages |
| 2012年06月06日 09:13:27 | mitya57 | create |
|