[Tickets #1410] RESOLVED: Message with 8 bit characters incorrectly shown, if message display refreshed

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=1410
-----------------------------------------------------------------------
 Ticket             | 1410
 Updated By         | Michael Slusarz <slusarz at mail.curecanti.org>
 Summary            | Message with 8 bit characters incorrectly shown, if message display refreshed
 Queue              | IMP
 Version            | 4.0.2
-State              | Feedback
+State              | Resolved
 Priority           | 1. Low
 Type               | Bug
 Owners             | Horde Developers
-----------------------------------------------------------------------


Michael Slusarz <slusarz at mail.curecanti.org> (2005-05-27 22:56) wrote:

All right, I finally verified this as a problem with multipart messages.  It
turns out that PHP 5's clone() doesn't seem to work the way I expect it to. 
Namely, the outermost part of the object is cloned but inner variables in
the object may remain linked outside of the cloned object.  To me, clone
means to create a new copy of the object that is completely independent of
the old object.  Seems like the PHP folk agree with me since there are
multiple bugs on this issue - See, e.g.:
http://bugs.php.net/bug.php?id=27268
So, for now, hack around this issue using serialize/unserialize combo which
does create a truly independent object.

This should fix the issue with seeing un-encoded characters when
replying/forwarding to mesages (that's the only place where i was seeing
this weirdness).