Re: RTF to RTF Compressed
From: Michael Tissington (michael_at_nospam.com)
Date: 11/25/04
- Next message: Tim Radford: "PR_OWNER_APPT_ID not always unique"
- Previous message: Dan Mitchell: "Re: RTF to RTF Compressed"
- In reply to: Dan Mitchell: "Re: RTF to RTF Compressed"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Nov 2004 15:12:03 -0800
Thanks, this does seem to work provided I remember to call Commit on the
uncompressed stream after writing it (that's the bit I was missing).
-- Michael Tissington http://www.oaklodge.com http://www.tabtag.com "Dan Mitchell" <djmitchella@yahoo.com> wrote in message news:Xns95ACA0D4A88Cdjmitchellayahoocom@207.46.248.16... > "Michael Tissington" <michael@nospam.com> wrote in news:OuBRo7z0EHA.824 > @TK2MSFTNGP11.phx.gbl: >> I have a stream containing RTF >> How can I convert it to RTF Compressed ? > > WrapCompressedRTFStream(.., MAPI_MODIFY, ..) should do it; from the docs: > > "If the MAPI_MODIFY flag is passed in the ulFlags parameter, the > lpCompressedRTFStream parameter must already be open for reading and > writing. New, uncompressed RTF text should be written into the stream > interface returned in lpUncompressedRTFStream. Because it is not possible > to append the existing stream, the entire message text must be written. " > > It's a bit of a roundabout way to do it, but this is the way, as far as I > can see. I don't know offhand if this'll work on streams that aren't > connected to the body properties of a message, but at worst create a > temporary message to do this stuff in, I guess. > > -- dan >
- Next message: Tim Radford: "PR_OWNER_APPT_ID not always unique"
- Previous message: Dan Mitchell: "Re: RTF to RTF Compressed"
- In reply to: Dan Mitchell: "Re: RTF to RTF Compressed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|