[Tickets #4043] RESOLVED: forward operation breaks ISO-8859-1 encoded subject line

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=4043
-----------------------------------------------------------------------
 Ticket             | 4043
 Updated By         | kimmo.liikonen at phnet.fi
 Summary            | forward operation breaks ISO-8859-1 encoded subject line
 Queue              | IMP
 Version            | 4.1.1
 State              | Bogus
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Michael Slusarz
+New Attachment     | subject-line-broken.JPG
-----------------------------------------------------------------------


kimmo.liikonen at phnet.fi (2006-06-28 01:22) wrote:

Correct description to this bug should be: Reply and forward operation
breaks ISO-8859-1encoded subject line, when default charset when reading
messages preference is set to ISO-8859-1.

Screenshot from reply operation is attached.

> No this is _NOT_ duplicate of that old bug. This is new bug and has 
> something to do with new feature which came in 4.1.1 (Added 
> preference for default charset when reading messages.). Because if I 
> set my default charset to UTF8, then subject is fine when i try to 
> reply or forward a message. if I set my default charset to 
> ISO-8859-1, then replying of forwarding the message breaks subject 
> line. The message is fine when i am viewing it. I can sent 
> screenshots of this, if you need them. The message is encoded with 
> ISO-8859-1.
>
> We set default charset to ISO-8859-1 when reading messages, because 
> many messages has broken headers, but content of it is encoded with 
> ISO-8859-1.
>
>> Verified that this works correctly in both HEAD and the latest
>> FRAMEWORK_3 builds.  I remember fixing this somewhere a long time
>> ago, but it is too late for me to try to figure out exactly where.
>> What is important is that it was fixed.  Marking as bogus and closing.
>