Tickets :: [#2357] us-ascii

6.0.0-beta13

4/11/26

Summary	us-ascii
Queue	MIMP
Type	Bug
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	vt (at) volkerthen (dot) com
Created	7/29/05 (7561 days ago)
Due
Updated	10/9/05 (7489 days ago)
Assigned	10/7/05 (7491 days ago)
Resolved	10/9/05 (7489 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09.10.2005 16:38:07	Jan Schneider	Comment #9 State ⇒ Resolved	Reply to this comment
Confirmed.

09.10.2005 16:26:42	Michael Slusarz	Comment #8	Reply to this comment
Chuck fixed the undefined $charset issue. And I think I really fixed the charset conversion of header information for real now.

08.10.2005 17:53:02	vt (at) volkerthen (dot) com	Comment #7	Reply to this comment
I updated compose.php and now I'm getting some error notices after sending a message: Notice: Undefined variable: charset in /var/www/html/horde-cvs/mimp/compose.php on line 375 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/horde-cvs/mimp/compose.php:375) in /usr/share/php/Horde/Mobile/Renderer/html.php on line 43 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/horde-cvs/mimp/compose.php:375) in /usr/share/php/Horde/Mobile/Renderer/html.php on line 45

08.10.2005 17:47:45	Jan Schneider	Comment #6	Reply to this comment
Nope, it's still in the UI charset here.

08.10.2005 16:06:09	Michael Slusarz	Comment #5	Reply to this comment
this should be fixed.

07.10.2005 08:59:14	Jan Schneider	Comment #4	Reply to this comment
The charset is set correctly in the Content-Type: header and MIME header encodings, but only the text body is converted from the UI charset to the message charset. Not so the subject header.

07.10.2005 05:36:09	Michael Slusarz	Comment #3 State ⇒ Feedback	Reply to this comment
try what i just committed.

02.10.2005 13:25:02	Chuck Hagenbuch	Comment #2 Assigned to Michael Slusarz Taken from Horde Developers	Reply to this comment
Michael, any thoughts on this?

29.07.2005 15:37:06	Jan Schneider	Assigned to Horde Developers State ⇒ Assigned

29.07.2005 15:29:10	vt (at) volkerthen (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ us-ascii Queue ⇒ MIMP State ⇒ Unconfirmed	Reply to this comment
I recognized that the character set used by default is us-ascii, but for example german umlauts in the subject and in the mail body are encoded with UTF-8. I think that's the reason why some mail clients (like Outlook Express) have problems with displaying these characters correctly. Shouldn't mimp's default charset be changed to utf-8?