[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              | Unconfirmed
+State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-03-18 13:48) wrote:

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.