Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.11

Request #3636 Allow specification of charsets and encoding
Submitted: 2005-02-28 14:14 UTC
From: jamesr at totalinfosecurity dot com Assigned: cipri
Status: Closed Package: Mail_Mime
PHP Version: 5.0.2 OS: Linux
Roadmaps: 1.4.0, 1.4.0a1    

 [2005-02-28 14:14 UTC] jamesr at totalinfosecurity dot com
Description: ------------ In creating an international webmail site, I needed to be able to specify the charset and encoding of each mime part separately. Therefore I have made modifications to your code which allow some more flexibility. Specifically: 1. You can specify encoding and charset for each mime part 2. You can specify content-disposition for attachments. This is necessary to allow multipart/text messages with several inline parts with different encodings. 3. The filename for attachments can now be encoded 4. The recipient (To: header) can now be encoded I have created two .diff files, one for mime.php and one for mimeDecode.php. Since it is difficult to modify someone else's code, I'm sure I made lots of mistakes and there were probably easier ways to do what I wanted, but after extensive testing with many multi-byte character sets, my changes appear to work in all cases. Please let me know what you think and if I made any mistakes, please also do correct me. Reproduce code: ---------------


 [2006-04-28 19:44 UTC] cipri (Cipriano Groenendal)
I've implemented most of the patches you've submitted. 1) Setting the encoding and charset of HTML/text parts is possible via the build_params passed to &get(). 2) Content-disposition on attachments has been implemented. 3) Encoded filenames for attachments has been implemented. 4) The To: header can now be encoded. THe only thing I could not make sense of is the multipart/text message with several inline parts. Could you send an example of such a mail to, so I can look at it and implement these fixes?
 [2006-04-28 21:33 UTC] cipri (Cipriano Groenendal)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.
 [2007-05-05 15:05 UTC] cipri (Cipriano Groenendal)
Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at Fixed in 1.4.0