Fri, 10 Apr 2026 01:05:01 +0000 https://bugs.horde.org/ticket/2702 Preference for default encoding I have a problem with the encoding in IMP when I? m reading Greek in a message from hotmail or Outlook. Both don?t include encoding information in the subject, while hotmail doesn?t as well include encoding headers information, which is responsible for the body of the message. Is there a way to include a drop-down menu in the message window with encoding options or the encoding in the above-mentioned cases to be selected automatically according to the chosen by the user language (e.g. ISO-8859-7 for Greek)? We are willing to contribute with code if necessary in order to provide this feature. Thu, 29 Sep 2005 08:30:24 +0000 https://bugs.horde.org/ticket/2702#t11981 I probably don't have to tell you that hotmail is sending completely broken messages. But this happens with so many mailers that it makes sense to define a default encoding for messages that don't define a proper charset. This has been requested several times, as such a feature exists in other mail clients too. I plan to implement this for a while already, but didn't get to it yet. A patch would be great. But this shouldn't be a selection in the message view, but a preference for all messages. Thu, 29 Sep 2005 08:41:54 +0000 https://bugs.horde.org/ticket/2702#t11985 First crack at this is now in HEAD and 4.1.1. It requires at least Horde 3.1.1. Tue, 21 Mar 2006 08:00:53 +0000 https://bugs.horde.org/ticket/2702#t17989 You also need to use the default charset for the email headers. Thu, 23 Mar 2006 17:22:01 +0000 https://bugs.horde.org/ticket/2702#t18060 > You also need to use the default charset for the email headers. So we have to run every header line through String::convertCharset()? In that case, we really need to change the preference defaults back to 'US-ASCII' rather than this code: 'value' => isset($GLOBALS['nls']['emails'][$GLOBALS['language']]) ? $GLOBALS['nls']['emails'][$GLOBALS['language']] : (isset($GLOBALS['nls']['charsets'][$GLOBALS['language']]) ? $GLOBALS['nls']['charsets'][$GLOBALS['language']] : 'ISO-8859-1'), Because those convertCharset calls are going to add up in a hurry. Fri, 24 Mar 2006 04:49:53 +0000 https://bugs.horde.org/ticket/2702#t18083 First attempt at converting headers has been completed. Fri, 24 Mar 2006 05:46:18 +0000 https://bugs.horde.org/ticket/2702#t18084 >> You also need to use the default charset for the email headers. > > So we have to run every header line through String::convertCharset()? > In that case, we really need to change the preference defaults back > to 'US-ASCII' rather than this code: > 'value' => isset($GLOBALS['nls']['emails'][$GLOBALS['language']]) > ? $GLOBALS['nls']['emails'][$GLOBALS['language']] > : (isset($GLOBALS['nls']['charsets'][$GLOBALS['language']]) > ? $GLOBALS['nls']['charsets'][$GLOBALS['language']] > : 'ISO-8859-1'), > Because those convertCharset calls are going to add up in a hurry. But they will do anyway if you use that feature, right? I can't really test it unfortunately, because Cyrus doesn't allow unencoded 8bit characters in headers anyway. Fri, 24 Mar 2006 09:34:45 +0000 https://bugs.horde.org/ticket/2702#t18089 > But they will do anyway if you use that feature, right? I can't > really test it unfortunately, because Cyrus doesn't allow unencoded > 8bit characters in headers anyway. The way you changed the preference, then yes. That's why I originally had the preference set to '' (for Default RFC Encoding) by default. If we would have a blank option, and ship with blank (i.e. us-ascii) as the default, then the 'default_charset' globals don't get set and none of the convertCharset() calls are triggered. I guess what I am trying to say is I believe we should ship with the default as 'US-ASCII' (i.e. replace the 'ISO-8859-1' entry with US-ASCII) since this is the "proper" RFC-compliant charset to use by default. Fri, 24 Mar 2006 15:53:36 +0000 https://bugs.horde.org/ticket/2702#t18107 Makes sense. Changed in CVS. Fri, 24 Mar 2006 15:58:43 +0000 https://bugs.horde.org/ticket/2702#t18110 All coding should be completed. Tests have been working for me. Enhancement has been completed so closing ticket - bug reports should go into new tickets. Fri, 31 Mar 2006 22:58:01 +0000 https://bugs.horde.org/ticket/2702#t18540