I suppose I didn't mean to *replace* the existing system in favour of this one, but rather augment markdown from one of it's stated goals: "...the single biggest source of inspiration for Markdown.s syntax is the format of plain text email." It's common practice to add^H^H^H put these makes in for clarity. In current Markdown they would be represented as normal text, but the intention of the writer is strikethrough. Perhaps there's no room in markdown for this enhancement in the name of a minor feature. This is understandable.
> Perhaps there's no room in markdown for this enhancement in the name of a > minor feature. This is understandable.It is entirely reasonable, I think, that some people want specific "minor" features that do not have broad enough support to make them standard (and thus a requirement for all implementations). This is the main reason why with python markdown we have focused on making it easy to add such features as extensions. The feature you are proposing is exactly the kind of things we've had in mind. - yuri -- http://spu.tnik.org/
In article <20090504101943.J24560 at maniac.deathstar.org>, John Kipling Lewis <markdown-discuss at six.pairlist.net> wrote:>It's common practice to add^H^H^H put these makes in for clarity.Common practice where? I used to see that construction on usenet, and occasionally I use it in mail, but in my experience the whole point of typing out ^H & ^W is so that your reader will see it and be amused by what you're writing. (I occasionally use strikethrough when writing on weblogs, but I don't think it looks as good as the visual attempt to frantically backspace over some intemperate but true invective.) And from a usability point of view, I don't think it's all that great because you'd need to keep track of how many characters you're backspacing over. -david parsons