[Tickets #9418] Re: Drafts headers are being badly encoded when they contain accented chars

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9418
------------------------------------------------------------------------------
  Ticket             | 9418
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Drafts headers are being badly encoded when they
                     | contain accented chars
  Queue              | IMP
  Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
-Owners             |
+Owners             | Jan Schneider, Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2010-12-01 01:34) wrote:

I can't reproduce. With the recent charset changes we ALWAYS assume  
that incoming data from the browser is in UTF-8.  So your draft  
message will ALWAYS be saved with the headers UTF-8 MIME encoded.  It  
doesn't matter what the charset dropdown selection in IMP is set to  
for drafts; obviously in dimp, data MUST be UTF-8 because of JSON  
encoding.

Sure enough, UTF-8 is now hardcoded into the saveDraft() function call  
(imp/compose.php:367).  Is your browser somehow sending ISO-8859-1  
instead?