[Tickets #11073] Re: Charset is not set for the "View Source"

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11073
------------------------------------------------------------------------------
  Ticket             | 11073
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Charset is not set for the "View Source"
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-03-13 04:53) wrote:

Again, no.  Here's a message that will be completely broken in the display:

Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: base64

The output message will be garbage

Here's another message that will be completely broken:

Content-Type: multipart/mixed; boundary=1

--1
Content-Type: text/plain; charset=iso-8859-1

[Text]

--1
Content-Type: text/plain; charset=utf-8

[Text]

--1--


Again, if you want a quick display of the part's contents THAT MAY  
**NOT** BE 100% ACCURATE, you can use View Source.  If you need the  
EXACT CONTENTS, you MUST use save as.

We do NOT guarantee that View Source outputs an accurate  
representation of the data.  Because that is impossible to do in the  
browser (or, for that matter, any text editor).  That's because MIME  
messages are NOT designed to be viewed as a single file!  A MIME  
message != a discrete file as is commonly used in an OS.