Message159363
| Author |
pitrou |
| Recipients |
Arfrever, Henri.Salo, Huzaifa.Sidhpurwala, asvetlov, benjamin.peterson, ezio.melotti, loewis, pitrou, serhiy.storchaka, vstinner |
| Date |
2012年04月26日.11:54:12 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1335441165.3421.1.camel@localhost.localdomain> |
| In-reply-to |
<1335440186.13.0.485206103926.issue14579@psf.upfronthosting.co.za> |
| Content |
> I ran tests of utf16_error_handling-3.2_4.patch on Python 3.1. Two tests are failing:
> - b'\x00\xd8'.decode('utf-16le', 'replace')='\ufffd\ufffd' != '\ufffd'
> - b'\xd8\x00'.decode('utf-16be', 'replace')='\ufffd\ufffd' != '\ufffd'
>
> I don't think that the test is correct: UTF-16 should resynchronize as
> early as possible (ignore the first invalid byte and restart at the
> following byte), so '\ufffd\ufffd' is the correct answer.
UTF-16 units are 16-bit words, not bytes, so '\uffffd' sounds correct to
me. You resynchronize on the word boundary: the invalid word is skipped.
> - with UTF-8 decoder: (b'\xC3' +
> '\xe9'.encode('utf-8')).decode('utf-8', 'replace') returns '\ufffd
> \xe9'
That's because UTF-8 operates on bytes: the invalid byte is skipped. |
|