similar to: Possible bug in Markdown.pl with `<<` handling

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 -->

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

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

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'm currently attempting to write a spec for parsing Markdown Extra, and since one goal is to minimize the differences in output between implementations, I've made a tool allowing me to compare who does what for any given input. I hope this can also facilitate future discussions about the syntax. So here's Babelmark, a testbed for various Markdown implementations were you

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

I was interested in going back to research past discussions on the list about possibilities for a syntax to add a class="foo" to div's and/or span's to Markdown text, but didn't have much luck. IIRC, the list never had a searchable web interface, but older posts were available on a Google search. This seems not to be the case any more. Can anyone recommend a good

It would be useful if defining headers (either Setext and atx style), if Markdown would also generate corresponding anchors: ## This is an H2 ## would create: <a name="This is an H2"/> <h2>This is an H2</h2> Or something like that. Or is that available some different way? Thanks, Jeremy C. Reed

I just received a [bug report] for Python-Markdown complaining that colons are used in the ids of footnotes. For reference, we [output] the same format at PHP Markdown Extra. The general complaint is that the colon in the id attribute (`id="fnref:1"`) causes jquery to choke when referencing that id from javascript because jquery uses colons to indicate pseudo elements (as does CSS). As

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,

Hello all, I've began writing the parsing section of the spec, and I though I'd let you know about where I'm heading with all this. Basically, parsing is defined as three consecutive passes: parsing document elements, parsing block elements and parsing span elements. Each pass is going to contain a set of rules the parser should attempt to match while parsing the input. Rules

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

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, >

This update to PHP Markdown fix a bug that slipped in the WordPress interface with the last update. It also introduce a new "feature": you can now instruct the parser to ignore HTML tags and/or entities in the input. You can do this by instantiating yourself the parser and setting the `no_markup` or `no_entities` properties to true: $parser = new Markdown_Parser;

Markdowners, just a short heads-up to a newly released Markdown implementation: "pegdown" (http://github.com/sirthias/pegdown) implements a Java Markdown-to-HTML processor based on a PEG parser with the grammar being based on John MacFarlanes C implementation "peg-markdown". pegdown uses "parboiled" (http://www.parboiled.org) for the actual parsing work and, as

Does anyone know which version of Markdown is best for Wordpress? I see online that there are a few and was wondering which one people prefer. Also, is there any chance John Gruber will write an official Markdown plugin for Wordpress, given how popular it's becoming? -------------------------------------------------------- robdumas at gmail.com http://obnoxio.us/

> Anyway, a spec for Markdown Extra would contain a spec for Markdown as > well, wouldn't it? I think the whole enterprise would be a lot more valuable, if we produce a combined spec, which would be self-contained, and call it Markdown 2.0. I don't think we necessarily need a formal grammar. What we need is to create a document, starting with "Markdown Syntax" perhaps,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm redesigning my site and considering moving from Movable Type to WP, but many of my entries are in Markdown. I really, really like Markdown and SmartyPants. I've not used Textile much, but Markdown feels more natural to me; also, I love SmartyPants because I'm a stickler for curly quotes. I understand there's a Markdown

Time for an update to PHP Markdown and PHP Markdown Extra. <http://michelf.com/project/php-markdown/> This new version of PHP Markdown Extra adds support for "fenced" code blocks (which I was previously calling "flat"). Fenced code blocks overcome many limitations of Markdown's indented code blocks: they can can be put immediately following a list item, can

This is a new release for PHP Markdown, following Markdown.pl 1.0.2b7 from a few weeks ago. It fix the same bugs, and some more; it also introduce more radical backend changes. It can be downloaded here: <http://www.michelf.com/docs/projets/php-markdown-1.0.2b7.zip> and you can test it on the PHP Markdown Dingus: <http://www.michelf.com/projects/php-markdown/dingus/> This