similar to: Searchable archives of Markdown discussion list still available?

It appears that Markdown will process ampersands contained within HTML comments if that comment is part of a markdown paragraph, but will not when that paragraph is contained within an HTML block of it's own (and therefore ignored by Markdown.) For example: This is a markdown paragraph with a comment that *will* be processed <!-- This & *will* be converted -->

MultiMarkdown 2.0.b1 includes an update to the core MultiMarkdown package, the Drag and Drop applications, the TextMate Bundle, and the Sample Document. There are a couple of significant changes in this release, as well as some bug fixes: * change \textwidth to \linewidth in LaTeX export XSLT files (let me know if this causes problems) * add Windoze compatibility to the perl scripts

So, hi all. First time commenting on the list. I personally think having tags (whether of type "author:" or type "by") is useful for two reasons. One: It allows multiple tags to be entered. Two, it clears up the potential problem listed by Fletcher regarding tags. by Christoph Freitag Affiliation: XYZ by Fletcher T. Penney Affiliation: ABC tags: Markdown, Standardization,

It appears that "double angles" are not properly converted when they are not in code blocks, if there is not a space following the second `<`. For example: This is not handled <<properly>>. But this <<is>>. As is << this>>/. becomes: <p>This is not handled &lt;<properly>>.</p> <pre><code>But

Begin forwarded message: > From: fletcher at fletcherpenney.net > Date: July 6, 2011 10:38:33 PM EDT > Subject: [MMD] MMD-Edit is progressing nicely > > MMD-Edit is progressing nicely > > 07/06/2011 22:31:22 > I am continuing work on my text editor for the Mac, MMD-Edit. It?s based on work described in another post, but briefly it performs syntax highlighting of

I am glad to see support for footnotes working its way into other implementations of Markdown! However, I have a couple of issues. Issue # 1. There appears to be a bug in the footnote parser that causes material following the footnote to be included as part of the footnote. For example: < Example Section > ## Metadata ## First, take a look at the overall structure of the document.

I know things have been quiet lately, but I wanted to announce a couple of MultiMarkdown related happenings: 1. I am in the process of creating a new website, and MultiMarkdown is one of the first things to be moved. The new address is <http:// fletcherpenney.net>. A new look, a new URL, some new technology, and some new content. I have not moved much from the old site yet, but

A lot of people have expressed interest in combining math features with Markdown, but I am not aware of any real developments from these requests. I was looking around and toying with [ASCIIMathPHP](http:// www.jcphysics.com/ASCIIMath/) and integrated it with MultiMarkdown and my xhtml2latex XSLT transforms. You can include math as an inline formula by using a markup similar to inline

I have released version 2.0.b5 of MultiMarkdown today. As always, it can be downloaded from: <http://files.fletcherpenney.net/MultiMarkdown.zip> Some of the changes include: * spaces at end of xslt filenames won't cause failure * use `\url{}` for "non-referenced" url's in LaTeX to allow linebreaks (though they still don't always break correctly --- this is a

sherwood said: > If agreement is reached, then the group > looks at variants 6,7,8,9 and inquires > if they would like to join in this effort. well, that kind of leveraged consensus would have been the way to go about this process a year ago. but not today. > Has anyone collected a would-be canonical list > of either the ambiguous cases in original MD, >

How can we improve URL detection in Markdown? I posted a question on Stack Overflow and happened to click a URL in my post. To my surprise, it wasn't functional, and it took three different, nonintuitive manipulations before I achieved a functional URL. Stack Overflow says "not my problem", so I'm deferring to Markdown itself. Here's a

Hi all, I'm a newer user of markdown & MultiMarkdown, and I'm looking for the perfect setup of software for my Mac and my Android phone. I'd like to have my drafts editable from both. What I want is an attractive Mac app for writing (primarily blog posts and emails) that saves its files as .txt . Most of them save as .md or .markdown instead, and since there doesn't seem to

looks like my message from last week about writing tools was right on time... we are enjoying a display of fireworks now going off in this particular arena... fletcher started work on an editing app with markdown-preview built right in, after reporting on his blog that he had "seen the future" in ali's post last month, where ali debuted his syntax highlighter, and fletcher is

big congratulations to fletcher penney on his release of "multimarkdown composer". at #21-paid when i purchased it just now. i'd say $9.99 will be best in the long-term -- don't listen to people who say more -- but $7.99 is the _right_ introductory price. word-of-mouth will be what sells this pup, so you want it to flow copiously right now. -bowerbird -------------- next part

Is there any way to pursuade markdown to create HTML link anchor targets? -- Make April 15 just another day, visit http://fairtax.org

Hi, because of the great editor "Writer" from Information Architects I've learned about Markdown and I love it. But it's very confusing, that there are so many standards with different features: classical Markdown, Markdown Extra, MultiMarkdown. I think for most users and the spreading of Markdown it would be nice, to have only one syntax. And this universal syntax should have

Hello, As I am using markdown to write documentation, I am often tempted to make links to terms in definition lists. Since this is not possible for now (at least in php markdown extra), I was wondering if this could be a common addition in major implementation supporting definition lists. the syntax would be term {#id} : definition This syntax tries to follows current convention and

ok, while i was in the process of writing that last post, fletcher and john weighed in themselves. that's good. i can say some things that they can't, though, so i will. fletcher told you how multimarkdown is booming, and it was an impressive list. what you might not realize is, he _undersold_ it. it is even bigger than he described, and it's gonna _double_ in size in the next

Dear fellow Markdown enthusiasts, As you all might know, Markdown is a highly context sensitive language that the (often regex-based) syntax highlighting mechanisms in existing editors struggle to keep up with. I have taken John MacFarlane's excellent peg-markdown compiler and modified its parser to function as an interpreter for syntax highlighting purposes. The end result is a

hey fletcher, thanks for your input here. :+) and -- quite obviously -- your program will be whatever it is that _you_ think that it should be. of course. the thing is, i am certain that i have been clear that the feature that i believe will be "killer" is on-the-fly formatted display. that's my stand. and i'd say my reasoning has been equally clear, namely that this