From andrew at logicalware.com  Fri Aug 19 15:03:38 2005
From: andrew at logicalware.com (Andrew Veitch)
Date: Fri, 19 Aug 2005 14:03:38 +0100
Subject: [Email-SIG] Text/Enriched - RFC 1896
Message-ID: <C45FA494-1349-4BB0-8647-B100E5CF4B3D@logicalware.com>

I notice that Apple Mail client generates text/enriched mail by  
default - see http://www.faqs.org/rfcs/rfc1896.html

It looks fairly straightforward to convert to HTML and there's some  
example C code in the RFC to do that.

It would be pretty useful to us to have a Python text/enriched to  
HTML convertor, I'm just wondering if it would be appropriate in the  
email library?

A

--
Logicalware Ltd
Stuart House, Eskmills, Musselburgh, EH21 7PQ, UK
Tel: +44(0)131 273 5130




From barry at python.org  Fri Aug 19 15:28:00 2005
From: barry at python.org (Barry Warsaw)
Date: Fri, 19 Aug 2005 09:28:00 -0400
Subject: [Email-SIG] Text/Enriched - RFC 1896
In-Reply-To: <C45FA494-1349-4BB0-8647-B100E5CF4B3D@logicalware.com>
References: <C45FA494-1349-4BB0-8647-B100E5CF4B3D@logicalware.com>
Message-ID: <1124458080.21907.79.camel@geddy.wooz.org>

On Fri, 2005-08-19 at 09:03, Andrew Veitch wrote:
> I notice that Apple Mail client generates text/enriched mail by  
> default - see http://www.faqs.org/rfcs/rfc1896.html
> 
> It looks fairly straightforward to convert to HTML and there's some  
> example C code in the RFC to do that.
> 
> It would be pretty useful to us to have a Python text/enriched to  
> HTML convertor, I'm just wondering if it would be appropriate in the  
> email library?

Would such a converter have a more general application?  Maybe a
separate Python module would be more useful; the email package could
then use it.

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: This is a digitally signed message part
Url : http://mail.python.org/pipermail/email-sig/attachments/20050819/bb29eba3/attachment.pgp

From fdrake at acm.org  Fri Aug 19 17:40:08 2005
From: fdrake at acm.org (Fred L. Drake, Jr.)
Date: Fri, 19 Aug 2005 11:40:08 -0400
Subject: [Email-SIG] Text/Enriched - RFC 1896
In-Reply-To: <1124458080.21907.79.camel@geddy.wooz.org>
References: <C45FA494-1349-4BB0-8647-B100E5CF4B3D@logicalware.com>
	<1124458080.21907.79.camel@geddy.wooz.org>
Message-ID: <200508191140.08505.fdrake@acm.org>

On Friday 19 August 2005 09:28, Barry Warsaw wrote:
 > Would such a converter have a more general application?  Maybe a
 > separate Python module would be more useful; the email package could
 > then use it.

An implementation of text/enriched certainly wouldn't need to rely on the 
email package, so it makes sense to use a separate module.  OTOH, I've never 
heard of text/enriched being used outside of email.  But separation of 
concerns suggests a separate module; I wouldn't expect the email package to 
be used for handling payload as more than a pile-o-bits, other than perhaps 
for message/*.


  -Fred

-- 
Fred L. Drake, Jr.   <fdrake at acm.org>