<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>us-ascii</title> 
  <pubDate>Fri, 10 Apr 2026 19:46:43 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/2357</link> 
  <atom:link rel="self" type="application/rss+xml" title="us-ascii" href="https://bugs.horde.org/ticket/2357/rss" /> 
  <description>us-ascii</description> 
 
   
   
  <item> 
   <title>I recognized that the character set used by default is us-as</title> 
   <description>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&#039;s the reason why some mail clients (like Outlook Express) have problems with displaying these characters correctly. Shouldn&#039;t mimp&#039;s default charset be changed to utf-8?</description> 
   <pubDate>Fri, 29 Jul 2005 15:29:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t10164</link> 
  </item> 
   
  <item> 
   <title>Michael, any thoughts on this?</title> 
   <description>Michael, any thoughts on this?</description> 
   <pubDate>Sun, 02 Oct 2005 13:25:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12028</link> 
  </item> 
   
  <item> 
   <title>try what i just committed.</title> 
   <description>try what i just committed.</description> 
   <pubDate>Fri, 07 Oct 2005 05:36:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12236</link> 
  </item> 
   
  <item> 
   <title>The charset is set correctly in the Content-Type: header and</title> 
   <description>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.</description> 
   <pubDate>Fri, 07 Oct 2005 08:59:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12246</link> 
  </item> 
   
  <item> 
   <title>this should be fixed.</title> 
   <description>this should be fixed.</description> 
   <pubDate>Sat, 08 Oct 2005 16:06:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12262</link> 
  </item> 
   
  <item> 
   <title>Nope, it&#039;s still in the UI charset here.</title> 
   <description>Nope, it&#039;s still in the UI charset here.</description> 
   <pubDate>Sat, 08 Oct 2005 17:47:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12269</link> 
  </item> 
   
  <item> 
   <title>I updated compose.php and now I&#039;m getting some error notices</title> 
   <description>I updated compose.php and now I&#039;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

</description> 
   <pubDate>Sat, 08 Oct 2005 17:53:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12270</link> 
  </item> 
   
  <item> 
   <title>Chuck fixed the undefined $charset issue.  And I think I rea</title> 
   <description>Chuck fixed the undefined $charset issue.  And I think I really fixed the charset conversion of header information for real now.</description> 
   <pubDate>Sun, 09 Oct 2005 16:26:42 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12283</link> 
  </item> 
   
  <item> 
   <title>Confirmed.</title> 
   <description>Confirmed.</description> 
   <pubDate>Sun, 09 Oct 2005 16:38:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2357#t12288</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
