-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Theo Van Dinter wrote: > On Fri, Aug 25, 2006 at 11:43:47PM +0200, decoder wrote: >> a) It is VERY hard to realize. To preserve the message, you would >> need two plugins, one that runs as first rule, converts the >> message to text only, and another one that runs as last rule and >> puts the image back into the message (so the message stays >> unchanged). > > Preserving the message isn't really a big deal. The internal > message tree format is for internal use only. It's not used when > writing out the message -- that's what the pristine parts are for. > So you *could* completely mess around with the tree if you wanted > to, it only affects the scan. > > It actually wouldn't be difficult to add in a "rendered" section > for image/* types, and have that included in the normal rules if > found. > > The main thing to do is make sure that the image is rendered into > text before the message body text array is cached -- and that's > solved (generally speaking) by doing the rendering in > check_start(). > > Heck, this may be worth having a new plugin call in M::SA::parse() > which happens right after the normal parsing run, called > render_parts or something, where plugins get called with the > message and main SA objects, and are expected to only generate > renderings for the non-standard types. > > Actually, that's not a bad idea. Feel like opening a BZ about it? > ;) >
Well, I guess I'm too busy to start another plugin now... but maybe someone else has the time.. Just don't remove the image ;) otherwise my plugin gets useless ;D Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE73aJJQIKXnJyDxURAu+bAKCEnCDQrCEormQ47HLo+6IdBOlTwQCgv90j iw7E9MqFO13bqmX05QN8HZU= =DsO+ -----END PGP SIGNATURE-----
