Message160561
| Author |
loewis |
| Recipients |
asvetlov, loewis, ned.deily, serhiy.storchaka, takluyver, terry.reedy |
| Date |
2012年05月13日.19:43:02 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<4FB00EC5.5040409@v.loewis.de> |
| In-reply-to |
<1336937620.25.0.911124372921.issue14777@psf.upfronthosting.co.za> |
| Content |
> But the encoding used seemingly depends on the source application -
> Geany (GTK 2, I think) seemingly sends UTF8 text anyway, whereas
> Firefox escapes the unicode character. So I don't think we can
> correctly decode the STRING value in all cases.
Ah, ok. IIUC, support for UTF8_STRING would also be in the realm of
the source application, right? If so, I think we should use something
more involved where we try UTF8_STRING first, and fall back to STRING
if the application doesn't support that.
This I could also accept for 2.7, since it "shouldn't" have a potential
for breakage. |
|