Message71057
| Author |
pitrou |
| Recipients |
gvanrossum, janssen, jimjjewett, lemburg, loewis, mgiuca, orsenthil, pitrou, thomaspinckney3 |
| Date |
2008年08月12日.16:04:38 |
| SpamBayes Score |
0.00029811743 |
| Marked as misclassified |
No |
| Message-id |
<1218557076.5539.16.camel@fsol> |
| In-reply-to |
<1218554429.43.0.154361702641.issue3300@psf.upfronthosting.co.za> |
| Content |
I agree that given two similar patches, the one with more tests earns
some bonus points. Also, it seems to me that round-trippability of
quote()/unquote() is a logical and semantic requirement: in particular,
if there is a default encoding, it should be the same for both.
> For future apps, this should almost certainly be UTF-8
> (if it isn't, the website won't be able to accept form input across all
> characters, so isn't Unicode compliant anyway).
Actually, it will be able to accept such form input, as characters not
supported by the charset should be entity-encoded by the browser (e.g.
"{").
I have no strong opinion on the very remaining points you listed, except
that IMHO encode_rfc2231 with charset=None should not try to use UTF8
by default. But someone with more mail protocol skills should comment :) |
|