Tickets :: [#8556] No longer possible to use different charsets for headers

6.0.0-beta1

7/3/25

Summary	No longer possible to use different charsets for headers
Queue	Horde Framework Packages
Queue Version	Git master
Type	Enhancement
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	09/06/2009 (5779 days ago)
Due
Updated	11/30/2009 (5694 days ago)
Assigned	09/28/2009 (5757 days ago)
Resolved	11/15/2009 (5709 days ago)
Milestone
Patch	No

11/30/2009 09:34:38 AM	Jan Schneider	Comment #7	Reply to this comment
Makes sense.

11/30/2009 06:58:05 AM	Michael Slusarz	Comment #6	Reply to this comment
Hm, not quite. I don't think specifying a charset for all headers different from the body is a big improvement. It was possible to specify different charsets for individual headers. This seems like overkill to me. In the rare case you want to specify per-header encoding different than the default, you can manually MIME encode that particular header in the desired charset before adding it to the Headers object (since if there are no non-ASCII characters in the value, the code won't try to auto-encode).

11/15/2009 11:53:17 AM	Jan Schneider	Comment #5	Reply to this comment
Hm, not quite. I don't think specifying a charset for all headers different from the body is a big improvement. It was possible to specify different charsets for individual headers.

11/15/2009 03:00:22 AM	Michael Slusarz	Priority ⇒ 2. Medium State ⇒ Resolved

11/15/2009 03:00:11 AM	CVS Commit	Comment #4	Reply to this comment
Changes have been made in Git for this ticket: ~~Request #8556~~: Allow specifying a header charset for a part http://git.horde.org/diff.php/framework/Mime/lib/Horde/Mime/Part.php?rt=horde-git&r1=6f52fd964be8cb39f0c370dd5c3de612cb1eae87&r2=6f82ed1e4005f034a1d9443e896d64726735c16f http://git.horde.org/diff.php/framework/Mime/package.xml?rt=horde-git&r1=ce37a8c96778f19ebea3d2e0dc8c14d7b6494c26&r2=6f82ed1e4005f034a1d9443e896d64726735c16f

11/05/2009 12:57:20 PM	Jan Schneider	Type ⇒ Enhancement State ⇒ Accepted Priority ⇒ 1. Low

09/28/2009 09:43:30 AM	Jan Schneider	Comment #3	Reply to this comment
It was possible, though it wasn't used anywhere in application code. From a library standpoint, I don't see why we shouldn't allow it though.

09/28/2009 04:14:41 AM	Michael Slusarz	Comment #2 State ⇒ Feedback	Reply to this comment
This wasn't possible in the previous (Horde 3) version either. And if it was, this was not by design.

09/06/2009 04:37:57 PM	Jan Schneider	Comment #1 Milestone ⇒ State ⇒ Assigned Patch ⇒ No Assigned to Michael Slusarz Queue ⇒ Horde Framework Packages Summary ⇒ No longer possible to use different charsets for headers Type ⇒ Bug Priority ⇒ 1. Low	Reply to this comment
Because message headers are automatically mime-encoded now in Horde_Mime_Part::send(), using the charset of the message part, it's no longer possible to used different charsets for different headers, or even a different charset for a header than for the message body.