Message230053
| Author |
martin.panter |
| Recipients |
Julian, akira, cvrebert, ezio.melotti, jleedev, martin.panter, ncoghlan, pitrou, rhettinger, serhiy.storchaka, vstinner |
| Date |
2014年10月27日.01:06:14 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1414371974.47.0.159866907893.issue17909@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
If you adjusted the detect_encoding() logic according to Pete Cordell’s table at the bottom of <http://www.ietf.org/mail-archive/web/json/current/msg01959.html>, it might work for standalone strings.
However since the RFC encourages UTF-8 for best interoperability, I wonder if any of this autodetection is necessary. It might be simpler to just assume UTF-8, or use the "utf-8-sig" codec. Or are there real cases where detecting UTF-16 or -32 would be useful? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年10月27日 01:06:14 | martin.panter | set | recipients:
+ martin.panter, rhettinger, ncoghlan, pitrou, vstinner, ezio.melotti, cvrebert, akira, Julian, serhiy.storchaka, jleedev |
| 2014年10月27日 01:06:14 | martin.panter | set | messageid: <1414371974.47.0.159866907893.issue17909@psf.upfronthosting.co.za> |
| 2014年10月27日 01:06:14 | martin.panter | link | issue17909 messages |
| 2014年10月27日 01:06:14 | martin.panter | create |
|