➜

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 vstinner
Recipients aronacher, georg.brandl, vstinner
Date 2011-01-22.13:14:01
SpamBayes Score 2.4971987e-08
Marked as misclassified No
Message-id <1295702057.43.0.910932691547.issue10980@psf.upfronthosting.co.za>
In-reply-to
Content 
RFC 5987 (Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters), August 2010:
http://greenbytes.de/tech/webdav/rfc5987.html#language.specification.in.encoded.words

<< 3.3 Language Specification in Encoded Words

Section 5 of [RFC2231] extends the encoding defined in [RFC2047] to also support language specification in encoded words. Although the HTTP/1.1 specification does refer to RFC 2047 ([RFC2616], Section 2.2), it's not clear to which header field exactly it applies, and whether it is implemented in practice (see <http://tools.ietf.org/wg/httpbis/trac/ticket/111> for details).

Thus, this specification does not include this feature. >>

Hum ok, Latin1 looks safe and enough.
History
Date User Action Args
2011-01-22 13:14:17vstinnersetrecipients: + vstinner, georg.brandl, aronacher
2011-01-22 13:14:17vstinnersetmessageid: <1295702057.43.0.910932691547.issue10980@psf.upfronthosting.co.za>
2011-01-22 13:14:01vstinnerlinkissue10980 messages
2011-01-22 13:14:01vstinnercreate