Tickets :: Comment on [#12127] utf-16 encoded text files MIME part header broken

* Your Email Address
* Spam protection	Enter the letters below: . ,. . .. ,.__ \./ \| \| \| \./ [__) \| \|___\|/\\| \| \| \
Comment	>> IIRC, this is a known limitation with uploading text data in >> browsers. Browsers rarely (if ever?) insert charset information into >> the Content-Type of the uploaded file. So we pretty much have to >> assume that the file being uploaded is the same charset as the >> browser (which is assumed to be the same charset the underlying OS is >> using). >> >> See, e.g., >> http://stackoverflow.com/questions/6459741/how-to-determine-if-uploaded-file-is-in-utf-8-or-utf-16 >> >> BOM's could potentially be used to fix this some of the time. But >> there's no guarantee they will exist, or won't be stripped/munged by >> some intermediate process. > > Many thanks Michael for your prompt response, but unfortunately the > reply misses the main point of the original bug report. Horde/IMP > wrongly encodes the metadata about the UTF16-LE encoded text file > attachment, i.e. the MIME headers describing the attachment then > contain UTF16-LE. Those headers should never ever contain NUL bytes > nor 8-bit data of any kind. That is the key problem. (This bug is not > about the difficulties detecting the correct charset). >
Attachment
Watch this ticket