From andrew at logicalware.com Fri Sep 2 22:07:00 2005 From: andrew at logicalware.com (Andrew Veitch) Date: Fri, 2 Sep 2005 21:07:00 +0100 Subject: [Email-SIG] Bounty Message-ID: We've posted a format=flowed bounty: http://www.logicalware.org/bounties.html I think we might also do one for the text/enriched that I mentioned recently. A -- Logicalware Ltd Stuart House, Eskmills, Musselburgh, EH21 7PQ, UK Tel: +44(0)131 273 5130 http://www.logicalware.com From andrew at logicalware.com Mon Sep 12 11:43:41 2005 From: andrew at logicalware.com (Andrew Veitch) Date: Mon, 12 Sep 2005 10:43:41 +0100 Subject: [Email-SIG] RFC 3676 / format=flowed Message-ID: <84296FAA-F1B2-41AB-B1FD-58C43259F11C@logicalware.com> Martijn Pieters has completed a release candidate of the format=flowed module I mentioned earlier. It's at: http://www.zopatista.com/projects/formatflowed/releases/0.9.0 We'd be grateful for any comments. Andrew -- Logicalware Ltd Stuart House, Eskmills, Musselburgh, EH21 7PQ, UK Tel: +44(0)131 273 5130 http://www.logicalware.com From mj at zopatista.com Sat Sep 17 22:29:05 2005 From: mj at zopatista.com (Martijn Pieters) Date: Sat, 17 Sep 2005 22:29:05 +0200 Subject: [Email-SIG] ANN: formatflowed 1.0.0 released Message-ID: <432C7C91.2050306@zopatista.com> The formatflowed.py python library provides en- and decoding functionality for `RFC 2646`_ and `RFC 3676`_ text, also called format=flowed text. The development of this library was generously sponsored by `Logicalware`_. Version 1.0.0 is available from the project homepage at: http://www.zopatista.com/projects/formatflowed Changes since 0.9.0 ------------------- Only metadata was changed, and a simple README.txt was added. .. _RFC 2646: http://www.faqs.org/rfcs/rfc2646.html .. _RFC 3676: http://www.faqs.org/rfcs/rfc3676.html .. _Logicalware: http://www.logicalware.com/ -- Martijn Pieters -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 256 bytes Desc: OpenPGP digital signature Url : http://mail.python.org/pipermail/email-sig/attachments/20050917/5ff67265/signature.pgp From janssen at parc.xerox.com Thu Sep 22 07:07:57 2005 From: janssen at parc.xerox.com (Bill Janssen) Date: Wed, 21 Sep 2005 22:07:57 PDT Subject: [Email-SIG] 8bit encoding for text/xml multipart parts Message-ID: <05Sep21.220801pdt."58617"@synergy1.parc.xerox.com> I'm using the Python 2.3.5 email.MIMEText.MIMEText class to package up some XML, charset=utf8, and it constantly generates base64-encoded parts. That's not what I want: I want 8bit. My application can handle it. One can get 8bit for problematic stuff like image/png, but not for text/xml. Why not? What's the design decision here? Looking at email.Message, I don't see any comments on point. Bill