RTF documents from Zope
zopists, Anyone have any luck with converting DTML/HTML stuff from inside Zope to RTF that can be sent to another party via email? I'm sure I'm not alone in the world searching for the document format that I can send to people that everyone can read. I though html would do it, but the Mimetools haven't been friendly in sending out readable attatchments. Any thoughts? -- Jason Spisak webmaster@hiretechs.com
Hi Jason, Find attached a html2rtf.pl file (a perl script, I know I know, but it's the only one I came across that didn't need Win machines). I've not tried this, just did a quick scan on the web. Let me know if you have any luck with it. Phil phil@philh.org -----Original Message----- From: jason@zope.org [mailto:jason@zope.org]On Behalf Of Jason Spisak Sent: Monday, September 27, 1999 7:58 PM To: zope@zope.org Subject: [Zope] RTF documents from Zope zopists, Anyone have any luck with converting DTML/HTML stuff from inside Zope to RTF that can be sent to another party via email? I'm sure I'm not alone in the world searching for the document format that I can send to people that everyone can read. I though html would do it, but the Mimetools haven't been friendly in sending out readable attatchments. Any thoughts? -- Jason Spisak webmaster@hiretechs.com _______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope (To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Thanks Phil. I had come across this before. I was hoping to do a format conversion from within Zope rather than going to the filesystem. But, I've come to the comclusion that it's not that HTML format isn't palattable enough, it's that the mime tag isn't displaying things as attachments. And that is prompting people to ask for a "more comaptible" format. Nothing is probably more universal than HTML. All my best, Jason
My personal experience with MIME attachments is to first send an email with mime attachment from an email program, view the message source and then work out what I need Zope to send. Just a quick and dirty method. :-) Chui Jason Spisak wrote:
Thanks Phil.
I had come across this before. I was hoping to do a format conversion from within Zope rather than going to the filesystem. But, I've come to the comclusion that it's not that HTML format isn't palattable enough, it's that the mime tag isn't displaying things as attachments. And that is prompting people to ask for a "more comaptible" format. Nothing is probably more universal than HTML.
All my best,
Jason
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Jason Spisak wrote:
zopists,
Anyone have any luck with converting DTML/HTML stuff from inside Zope to RTF that can be sent to another party via email? I'm sure I'm not alone in the world searching for the document format that I can send to people that everyone can read.
plain ascii with chars >128 coded ä->"a is the only one that everyone can read, or at least that all mail programs can display. simple HTML is close behind
I though html would do it, but the Mimetools haven't been friendly in sending out readable attatchments.
Where do you use Mimetools in the chain - is Zope's mailhost with its mime support not enough
Any thoughts?
I don't think that RTF is more universally readable than HTML. And from your description it seems that the problem is not in encoding (HTML or RTF), but in packaging (by Mimetools). If you insist on using RTF, then DTML is very usable for generating that too, as DTML is quite format-agnostic, for it it is just text anyhow ;) -------------- Hannu
Hannu,
Where do you use Mimetools in the chain - is Zope's mailhost with its mime support not enough
I use the mime tag, but what it sends is not readable by all mail readers. I use this code: <!--#sendmail smtphost="mail.mydomain.com"--> From:<<!--#var email_from-->> Subject:<!--#var email_subject--> To:<<!--#var email_to-->> <!--#mime type=text/plain encode=7bit--> <!--#email_body--> <!--#boundary type=text/html disposition=attachment encode=base64--> <!--#var my_document--> <!--#/mime--> <!--#/sendmail--> What shows up for the second part is this: --192.168.8.9.503.18816.937995265.266.30862 Content-Type: text/html Content-Disposition: attatchment Content-Transfer-Encoding: base64 PEhUTUw+PEhFQUQ+PFRJVExFPkhUTUwgUmVzdW1lPC9USVRMRT4KICAgPE1FVEEgSFRUUC1FUVVJ Vj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9aXNvLTg4NTktMSI+ CjwvSEVBRD48Qk9EWSBCR0NPTE... etc, etc, etc... It's not a downloadable attatchment. The mime tag isn't doing something right.
I don't think that RTF is more universally readable than HTML.
I wholeheartedly agree. It's just that uneducated people are seeing this base64 encoding, (or in 7bit it comes out as HTML code) and insisting that it needs to be readable by MSword. blah, blah. I want to do it with html, but mimetools is preventing a lot of people form receiving it. All my best, Jason Spisak webmaster@hiretechs.com
Jason Spisak wrote: [snippage]
<!--#boundary type=text/html disposition=attachment encode=base64-->
[snipt]
--192.168.8.9.503.18816.937995265.266.30862 Content-Type: text/html Content-Disposition: attatchment Content-Transfer-Encoding: base64
This is an utter guess, but is the second quoted bit here an actual cut&paste and the first bit a reconstruction? I ask because "attachment" is misspelled in the header, but not in your tag, and they ought to be identical. If it is really misspelled in both, that could be your problem.
Evan, I used to have it spelled that wrong way. It was a copy paste from an old mail. The code is a direct cut/paste. Here I'll send you one from Zope so you can see. jason
Jason Spisak wrote: [snippage]
<!--#boundary type=text/html disposition=attachment encode=base64-->
[snipt]
--192.168.8.9.503.18816.937995265.266.30862 Content-Type: text/html Content-Disposition: attatchment Content-Transfer-Encoding: base64
This is an utter guess, but is the second quoted bit here an actual cut&paste and the first bit a reconstruction?
I ask because "attachment" is misspelled in the header, but not in your tag, and they ought to be identical. If it is really misspelled in both, that could be your problem.
Jason Spisak webmaster@hiretechs.com
participants (6)
-
Chui.Tey@env.qld.gov.au -
Evan Simpson -
Hannu Krosing -
Jason Spisak -
Jason Spisak -
Phil Harris