Bug#450674: Handling invalid UTF-8 in reportbug

[brian m. carlson]

I'm going to assume that your bug report is about the fact that reportbug is not gracefully handling the invalid UTF-8 that it was handed, which admittedly is a problem. (If this is not, in fact, the problem, please correct me.)

--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
a typesetting engine: http://crustytoothpaste.ath.cx/~bmc/code/thwack
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

I don't know if there is a way for reportbug to continue on once invalid character data is placed in the subject field, since it cannot encode it, and email standards do not allow unencoded 8-bit data in headers. I think the best way to handle this is to make python's email module set errors to 'replace' when converting to unicode, so that invalid UTF-8 will be autoconverted to U+FFFD. Thoughts?

signature.asc
Description: Digital signature