similar to: PHP Markdown 1.0.2b7

>>> I'm not sure the indentation feature is so useful. After all, you >>> can use the old syntax if you want indentation. What do you think? >> >> I'd prefer to keep it simple and leave out the indentation feature. I would also prefer to leave this out. >>> Perhaps an alternative would be to use ++++s instead of ~~~~s. >> Advantages: Not

Along with the new release of PHP Markdown 1.0.2b7 comes this new version of PHP Markdown Extra. It contains every improvements of PHP Markdown 1.0.2b7 plus some new fixes and two new features. You can download it here: <http://www.michelf.com/docs/projets/php-markdown-extra-1.1b1.zip> and you can test it on the PHP Markdown Dingus (select PHP Markdown Extra):

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

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

This is basically a pre-announcement. I'll make the announcement more official by posting it on my blog when it goes out of beta. There's a new branch to PHP Markdown. It contains the two exact same parsers found in PHP Markdown and PHP Markdown Extra, but without all the cruft. In other words: is packaged to be used as a library, and only as a library. The two parsers classes are in the

I decided 1.0.1d would be about fixing bugs. PHP Markdown 1.0.1d is simply version 1.0.2b7 with a couple more bug fixes and some features disabled. I disabled support for [this] as a synonym for [this][] because it's still labeled as experimental and because it's nowhere to be found in the documentation yet. The `markdown="1"` hack added to 1.0.2b7 has been disabled

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;

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

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

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

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

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

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

I'm announcing today a new testsuite application for Markdown called MDTest. I've been using it as a replacement for John's Markdown Test for some time now I think it's ready for release. First, I want to say Markdown Test has been very useful in developing PHP Markdown. The testsuite covers many cases, however I still found the need to add other tests for PHP Markdown, to

My fork of Michel Fortin's PHP Markdown Extra has been updated to include support for MathJax as well as jsMath. Both of these are JavaScript libraries for using LaTeX syntax, e.g., \(E = mc^2\), to include high quality, scalable equations (not just bitmapped images of equations) in your HTML pages. Links to more information: * A [description of PHP Markdown Extra Math][1], along with some

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

Bug fixes for PHP Markdown & Extra, available as beta version for now. You can download them from these URLs. <http://www.michelf.com/docs/projets/php-markdown-1.0.2b8.zip> <http://www.michelf.com/docs/projets/php-markdown-extra-1.1.3b1.zip> One noticeable change in these releases is that PHP Markdown now outputs numeric character references for escaped characters (like

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

I've fixed some bugs in PHP Markdown Extra 1.1b1, the most important ones relating to footnotes. Thank you for the feedback. So here you can download the second beta: <http://www.michelf.com/docs/projets/php-markdown-extra-1.1b2.zip> 1.1b2 (21 Sep 2006) * Changed the space before footnote backlinks to an unbrekable space `&#160;` at the suggestion of John Gruber. *