similar to: PHP Markdown 1.0.1l & Extra 1.2

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

This is the first release of PHP Markdown Lib. This package requires PHP version 4.3 or later and is designed to work with PSR-0 autoloading and, optionally, with Composer. You can download it from the PHP Markdown website: <http://michelf.ca/projects/php-markdown/> You can also read the official announcement here: <http://michelf.ca/blog/2013/php-markdown-lib/> Also note new

I'd like to announce a beta release of the Fenced-Code-Blocks Extension for Python-Markdown. <http://www.freewisdom.org/projects/python-markdown/Available_Extensions> The latest code for Python-Markdown and packaged extensions are now available on Gitorious. <http://gitorious.org/projects/python-markdown> The same syntax is used as the just released PHP Markdown Extra 1.2. I

Howdy, Quick question: Since list items with multiple paragraphs need to be indented four spaces, and code blocks are also indented four spaces, is there any way to disambiguate a list followed by a code block? Example: * This is a list item. * And so is this. Is this a second paragraph in the second list item, or a code block? It looks like Markdown.pl and discount

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

I've rewritten the code block grammar in the Markdown Extra [spec][] to match what Markdown.pl and PHP Markdown do. It should now handle things such as this: ~~~ > One Two > Three Four Five ~~~ as one blockquote containing only one code block with five lines, equivalent to this one (using fenced code blocks instead for clarity): ~~~ > One >

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

It took much more time than I expected, and it is currently less complete than I have hoped, but I've finaly made a first draft of the Markdown Extra spec. You can find it at <http://michelf.com/specs/markdown-extra/ > Currently, the specification defines its goals and a document model for Markdown Extra. It lacks the most important part though: the parsing section, which

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;

http://babelmark.bobtfish.net/?markdown=%3Ca%2Bb%40c.org%3E&normalize=on Only Python markdown, Pandoc, discount and PEG markdown seem to get this 'right'. As a + is perfectly valid in email addresses, I'm going to fix this in my modules. This was reported to me via the cpan.org RT (37909), and I thought I'd share as it's a good one in Babelmark. Cheers Tom

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

The following benchmarks have been obtained using the TextMate manual as the input source: <http://macromates.com/textmate/manual/source.tbz> Using PHP Markdown, parsing the 24 files separately (with the reference file appended to each of them), I get this (on an iBook G4 1.2 Ghz): Total Avg. Min. Q1. Med. Q3. Max. Parse Time (ms):

This is something that I've been asked for many times. So today I'm announcing that all future versions of PHP Markdown and PHP SmartyPants will be encapsulated in a parser class. This has two major benefits: 1. It should make extensions to the syntax easier to create and maintain as it is now possible to now extend the parser by replacing (overriding) only the relevant

Until today, the only way I offered PHP Markdown and PHP Markdown Extra was with packaged zip files available on my website. It turns out, unsurprisingly, that some people would prefer a simpler path for keeping their copy of PHP Markdown up-to-date. So today I announce two additional ways of grabbing PHP Markdown and PHP Markdown Extra. The first one is a PEAR channel which can be used

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

Hello! On the markdown site it is written: "Markdown?s syntax is intended for one purpose: to be used as a format for writing for the web.", although recently I moved from Emacs Muse to Markdown markup for writing my study notes and plan to use it for writing technical documentation as well. However, in order to be able to use the features I had in Muse, I write using

I just received a report [1] that the footnote output we use in Python-Markdown (an exact copy of PHP Markdown Extra [3]) is not valid HTML [3]. If you notice he's using HTML5. At least the footnote syntax does valid on XHTML1 or HTML4. Anyway, any suggestions on how the various footnote implementations want to move forward with this? [1]: https://github.com/waylan/Python-Markdown/issues/129

I just realised I hadn't updated the version of PHP Markdown and Extra on the dingus as I pretended I did in my two announcements. It is now fixed: PHP Markdown 1.0.2b7 and PHP Markdown Extra 1.1b1 can now be tested on the dingus. <http://www.michelf.com/projects/php-markdown/dingus/> Sorry for any inconvenience. Michel Fortin michel.fortin@michelf.com http://www.michelf.com/

I'm using Markdown in an app and would like to provide support for including a table of contents. Any suggestions for a syntax? Has anyone done this before? My first thoughts are: 1. Have a special header item (using markdown extra's header syntax), e.g. generate-contents: yes 2. Have a special xml tag with optional alternative text inside, e.g. <contents> 1. First thingy 2.

Question: what should be the output for this: > for me the point of having my blog as a static site is mainly easy deployment<br> > I don't have to worry about even configuring PHP<br> > I just put html on a web server and boom! instant win > > <footer>? [Igor Wiedler wins](https://igor.io)</footer> The real question is how to treat