Yes, that does sounds ideal. Auto splitting attachments, plain and html text into into their own tiddlers so you could choose to import or discard, very cool.
After doing a bit of reading about deserializers being part of the TW core, it also sounds well above my current abilities. :-) Thanks for the note, though, it proves I wasn't missing something obvious. On 2/2/2018 3:53 AM, Jeremy Ruston wrote: Hi furicle, It sounds like the best solution would be create a tiddler deserializer for the message/rfc822 format. A deserializer is a JavaScript function that generates tiddlers given a block of text and a MIME type. The message/rfc822 format can contain multiple blocks of content (eg, a message and the attached images) which would be converted into separate tiddlers. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d2d2fbb2-3f2f-4270-9575-443015b36b4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
