Wed, 08 Apr 2026 03:27:13 +0000 https://bugs.horde.org/ticket/1591 utf-8 mime encoding I check out source of message, sended by Imp, and found string like this "Subject: =??b?0L/RgNC+0LLQtdGA0LrQsA==?=". As it's a utf8-encoded subject, why it not contain "=?utf-8?" at begin? Some mail clients may not correct detect encoding of this message. Mon, 21 Mar 2005 15:42:27 +0000 https://bugs.horde.org/ticket/1591#t6483 Works fine here. Mon, 21 Mar 2005 16:02:37 +0000 https://bugs.horde.org/ticket/1591#t6485 Sorry, it's my mistake. I set up locking for "sending_charset" in imp/prefs.php without defining any "value". Then, I have another question - setting that value to, for example "windows-1251", I see that charset is used for encoding headers, but filenames in attachments still encoded with UTF-8. If it right, can I change default encoding for filenames? Mon, 21 Mar 2005 16:33:56 +0000 https://bugs.horde.org/ticket/1591#t6491 That should be fixed. Mon, 21 Mar 2005 16:42:56 +0000 https://bugs.horde.org/ticket/1591#t6492 Can you try what i just committed to CVS? Tue, 22 Mar 2005 07:40:29 +0000 https://bugs.horde.org/ticket/1591#t6522 Am using stable version of Horde/Imp, not Head. Can I try get some file from cvs, or I must get whole tree? If I can - what file? Tue, 22 Mar 2005 16:04:23 +0000 https://bugs.horde.org/ticket/1591#t6531 Either somebody that is running head should confirm this fix works for them or you will have to manually patch the files (which shouldn't be too hard since framework is pretty well synced with HEAD at this point and there isn't more than 5 or 6 lines that changed). I just wanted feedback from someone before I merged this with stable. Wed, 23 Mar 2005 04:01:07 +0000 https://bugs.horde.org/ticket/1591#t6559 Well, it's working just fine for me so, due to the lack of feedback, I'm going to go ahead and commit it to 4.0.3. Fri, 25 Mar 2005 00:08:31 +0000 https://bugs.horde.org/ticket/1591#t6623 This patch didn't help, the attachment names are always sent as utf-8 if this is the UI charset. Wed, 13 Apr 2005 17:29:54 +0000 https://bugs.horde.org/ticket/1591#t7279 This for real should be fixed now (it was actually a bug in Horde - framework/MIME/MIME/Part.php) and has been fixed in 3.0.5. Thu, 14 Apr 2005 07:08:44 +0000 https://bugs.horde.org/ticket/1591#t7304 No. It's now encoded in the charset that the user has set in his preferences, not in the charset that he selected in the compose screen. If I select a different charset in the compose screen *before* uploading the attachment, the correct charset is used in the header encoding, but the filename is not converted from the UI charset to the selected. Thu, 14 Apr 2005 10:44:38 +0000 https://bugs.horde.org/ticket/1591#t7309 Did I finally get this right? http://lists.horde.org/archives/cvs/Week-of-Mon-20050509/044614.html Thu, 12 May 2005 05:26:56 +0000 https://bugs.horde.org/ticket/1591#t8127 Still no go. My tests are with a UTF-8 encoded file name containing Traditional Chinese letters. I test sending the attachment with three different charsets, latin1 - my default one, utf-8 and big5; both specifying the email charset before and after uploading the attachment. The only case that works is if i set the email charset to utf-8 before uploading the attachment. All other cases fail. The latin1 tests must fail of course. Thu, 12 May 2005 12:09:52 +0000 https://bugs.horde.org/ticket/1591#t8131 Ah, and i always use utf-8 on the browser side of course, so the filename should always be in utf-8. Thu, 12 May 2005 12:10:46 +0000 https://bugs.horde.org/ticket/1591#t8132 My mistake. I forgot to take out the code that was setting the filename to the sending character set. I've fixed it so that this filename is always stored in the character set of the browser (i.e. NLS::getCharset()). Hopefully, this fixed it (*cringe* - thanks for your patience). Thu, 12 May 2005 15:45:19 +0000 https://bugs.horde.org/ticket/1591#t8135 Great! Works now in all combinations. Thanks for not giving up! :-) Thu, 12 May 2005 16:07:48 +0000 https://bugs.horde.org/ticket/1591#t8136