Using the rev function base64decode() and then writing to a binfile, I can make it work. I guess I would feel more comfortable working from the standard versus my observations. (AppleScript could tell Expander to do it for me but I would still need a Windows way.) Does anyone know which RFC, or something else, that defines the formatting of attachments ?
In a message dated 3/29/04 11:24:11 PM, Sarah Reichelt < [EMAIL PROTECTED]> writes: > > Hi Chris, > The encoding just reads the file as binary data, then uses > base64encode. If you did the reverse, remembering to save as a binfile, > I reckon it should work no matter what the file type. > > If you wanted to use Stuffit Expander instead, I have a technique I use > sometimes for Apple Mail when attachments don't display properly, but > just come through in their encoded form. I select the encoded section > (from one boundary marker to the next), copy and paste it into a text > editor, then save the file as "whatever.hqx". If you then double-click, > Stuffit Expander will decode it correctly. > > Cheers, > Sarah > > On 30 Mar 2004, at 7:33 am, [EMAIL PROTECTED] wrote: > > > I am playing with the 'POP library' stack (thank you and kudos to > > Sarah) and it's time to decode the attachments. I can write > > my own decodes for the easy ones, like TXT and HTML, > > but I would like to better understand the format and > > do something that could be reused by others. > > Has anyone already done this ? > > And/or know which RFC defines the standard ?�� Thank you ... Chris _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
