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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12127
------------------------------------------------------------------------------
  Ticket             | 12127
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | utf-16 encoded text files MIME part header broken
  Queue              | IMP
  Version            | 6.0.4
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-03-27 00:17) wrote:

> 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).

But this is still potentially an issue similar to what I described.   
For example: the browser may send UTF-16 as the charset, but the PHP  
conversion methods mishandle it since that is NOT the charset that the  
text really is.  And/or the fact that PHP string conversion methods  
are known to be buggy with UTF16LE (i.e. iconv() on certain systems).

At a minimum, I need an example file that triggers this behavior.   
Might want to zip/tgz before adding to the ticket to prevent the data  
from being munged.