Message118439
| Author |
loewis |
| Recipients |
eric.araujo, gyorkop, loewis |
| Date |
2010年10月12日.17:17:02 |
| SpamBayes Score |
0.00043385266 |
| Marked as misclassified |
No |
| Message-id |
<1286903824.26.0.894978642089.issue10066@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The patch is incorrect. Even though this may let get these characters "through", the other end will have no clue that \x is meant as an escape.
Please face the ugly truth: XML (and hence XML-RPC) just does not support these characters, see http://www.w3.org/TR/REC-xml/#NT-Char
This is fixed slightly in XML 1.1 (which allows to refer to these characters by character reference), however, XML 1.1 is not used for XML-RPC, so this is not an option.
I'm closing this as "won't fix". If there is interest in doing something about it, I could accept a patch that rejects non-Char characters with an exception, instead of sending ill-formed XML. I'd recommend to use a regular expression for that. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年10月12日 17:17:04 | loewis | set | recipients:
+ loewis, eric.araujo, gyorkop |
| 2010年10月12日 17:17:04 | loewis | set | messageid: <1286903824.26.0.894978642089.issue10066@psf.upfronthosting.co.za> |
| 2010年10月12日 17:17:03 | loewis | link | issue10066 messages |
| 2010年10月12日 17:17:02 | loewis | create |
|