- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Sun, 04 Dec 2011 21:41:32 +0100
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: WebApps WG <public-webapps@w3.org>
* Henri Sivonen wrote: >Browsers don't support UTF-32. It has no use cases as an interchange >encoding beyond writing evil test cases. Defining it as a valid >encoding is reprehensible. If UTF-32 is bad, then it should be detected as such and be rejected. The current idea, from what I can tell, is to ignore UTF-32 exists, and treat content that clearly is UTF-32 as UTF-16-encoded, which is much worse, as some components are likely to actually detect UTF-32, they would disagree with other components, and that tends to cause strange bugs and security issues. Thankfully, that is not a problem in this particular case. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Sunday, 4 December 2011 20:41:57 UTC