For me, Kee is highlighting my dilemma: I need to reply to HTML, and create 
well-formed HTML tables and such, and in doing so the email needs to look good 
to the corporate/outlook world I live in.  I was actually going to spend time 
today searching the listserve for guidance. I've tried some other email apps 
and keep coming back the MM because of its unparalleled search.  But for us MM 
users that are even afraid of "keybinding", I keep hoping some sort of easily 
adopted solution will appear. Plaintext simply doesn't work for me in 25% of my 
life...

Rob McClure
shar...@gmail.com

> On Apr 6, 2014, at 9:36 AM, "Kee Hinckley" <kee+fre...@hinckley.com> wrote:
> 
> On 3 Apr 2014, at 11:16, Benny Kjær Nielsen wrote:
> 
> To me the question should be: Is it worth adding the option of alternative 
> Markdown converters at the price of people using inline HTML and other 
> unreadable plain text? I’m not so sure ;-)
> 
> Personally, I’m happy to keep using my wrapper around MultiMarkdown in the 
> existing model. It’s too complicated for it to be likely of use to others, 
> although if there were a way to release it as a bundle, I’d be happy to. But 
> it’s allowed me to do things like add automatic syntax-highlighting to code 
> blocks, and support tab-delimited tables, and otherwise extend my email in 
> ways which make my work much easier. If someone were to view the plain-text 
> of those messages, or even reply to them, they wouldn’t get exactly what I 
> got, but they’d get something perfectly readable–that’s the basic nature of 
> Markdown. I don’t think you need to specially tag those situations. Assume 
> that in the future other mail programs might use other markdown processors; 
> you want them to interact.
> 
> If you’re looking at where to focus, rather than specifically supporting 
> other Markdown processors, I’d focus on supporting people who have to reply 
> to HTML email without losing the original HTML. I effuse to people at work 
> about MailMate, but then I tell them they can’t use it–because it really 
> doesn’t work in a corporate environment where people are sending complex (and 
> often Outlook-generated) mail messages, and my current hack (strip out the 
> header information, convert body to a div, force-include MailMate’s CSS so as 
> to override the broken Outlook CSS for my portion of the message, and then 
> enter my markdown message above the raw HTML of their message) doesn’t work 
> with Sundown, and while it is fine for me, it’s not suitable for public 
> consumption. I only do that for work email, but it would nice to be able to 
> use it as a general reply option–because sometimes people send you HTML email 
> and you need to reply without bowdlerizing it. Forcing top-commenting in that 
> environment is probably fine (I rarely see Outlook users inline 
> commenting–and when they do, it invariably gets screwed up by Outlook–but 
> maybe that’s just where I work).
> 
> _______________________________________________
> mailmate mailing list
> mailmate@lists.freron.com
> http://lists.freron.com/listinfo/mailmate
_______________________________________________
mailmate mailing list
mailmate@lists.freron.com
http://lists.freron.com/listinfo/mailmate

Reply via email to