| Summary | wrong charset of subject on reply/forward |
| Queue | IMP |
| Queue Version | 4.1.1 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | miksir (at) maker (dot) ru |
| Created | 4/26/06 (7369 days ago) |
| Due | |
| Updated | 4/28/06 (7367 days ago) |
| Assigned | |
| Resolved | 4/28/06 (7367 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
bug 3765.State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ wrong charset of subject on reply/forward
Queue ⇒ IMP
$header['subject'] = $imp_headers->getOb('subject', true);
'true' here mean mime decode and charset recode to default message
charset (in horde/lib/Horde/MIME/Headers.php:704). As result,
MIME-encoded header conver charset first on MIME::decode and then
convert charset again.
Quick solution for me - changes in compose.php:
- $header['subject'] = $imp_headers->getOb('subject', true);
+ $header['subject'] = $imp_headers->getOb('subject');
+ $header['subject'] = MIME::decode($header['subject']);