* Glenn Adams wrote: >What do you mean by "treat content that clearly is UTF-32 as >UTF-16-encoded"? Do you mean interpreting it as a sequence of unsigned >shorts? That would be a direct violation of the semantics of UTF-32, would >it not?
Consider you have ... Content-Type: example/example;charset=utf-32 FF FE 00 00 ... Some would like to treat this as UTF-16 encoded document starting with U+0000 after the Unicode signature, even though it clearly is UTF-32. -- Björn Höhrmann · mailto:bjo...@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/