I mean, I use Pelican's Markdown support in my own blog, but I wouldn't be unhappy about having to use <i> instead of underscores.
I mean, I use Pelican's Markdown support in my own blog, but I wouldn't be unhappy about having to use <i> instead of underscores.
Basically, markdown has (at least) two use-cases:
1. A safe (if you do HTML sanitization properly) way to let people mark-up their input on web comment sites like HN, StackOverflow, etc. This is probably the most common use-case.
2. A web authoring tool. This was the intended use-case.
Supporting arbitrary HTML is absolutely inadmissible for (1); not having arbitrary HTML is basically inexcusable for (2). And yeah, I could write the posts in straight HTML, but honestly that's a pain. Why shouldn't there be a tool that makes writing styled-text-with-lists-and-headings easy but lets me drop down to HTML when I need to?
I'm not actually sure I believe this yet. But I think I'd see a lot more use case for something that lets me do a very tiny amount of things, maybe just headings and bold and italic, and avoids not only ambiguity but any risk of ambiguity.
It just feels like we've reinvented HoTMetaL (https://support.novell.com/techcenter/articles/img/ana199609...) but with bonus ambiguity.
When you build that, let me know. Until then I'll be over here, using a Perl script from 2004 that still works just fine.
I also use markdown for writing blog posts, and have a lot of the same pain points. I have been working on an extended version of markdown (https://github.com/alexbecker/blogdown) to fix this.