Message 120266 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	eric.araujo, jelie, pitrou, r.david.murray
Date	2010-11-02.22:14:24
SpamBayes Score	7.714646e-05
Marked as misclassified	No
Message-id	<1288736067.75.0.46823280161.issue10284@psf.upfronthosting.co.za>
In-reply-to

Content
> And my text string is "\xC9ric", that's all. You mean b"\xC9ric", right? > If you look at the source of the articles, you will for instance see > that the Subject: header field is not MIME-encoded. It is directly > written in gb2312. How is an NNTP client supposed to guess the encoding? Either a header is MIME-encoded, or it follows the RFC 3977 recommendation of UTF-8 (“The content of a header SHOULD be in UTF-8”), or it's unreadable.

> And my text string is "\xC9ric", that's all.

You mean b"\xC9ric", right?

> If you look at the source of the articles, you will for instance see
> that the Subject: header field is not MIME-encoded.  It is directly
> written in gb2312.

How is an NNTP client supposed to guess the encoding? Either a header is MIME-encoded, or it follows the RFC 3977 recommendation of UTF-8 (“The content of a header SHOULD be in UTF-8”), or it's unreadable.

History
Date	User	Action	Args
2010-11-02 22:14:27	pitrou	set	recipients: + pitrou, eric.araujo, r.david.murray, jelie
2010-11-02 22:14:27	pitrou	set	messageid: <1288736067.75.0.46823280161.issue10284@psf.upfronthosting.co.za>
2010-11-02 22:14:24	pitrou	link	issue10284 messages
2010-11-02 22:14:24	pitrou	create