similar to: PHP Markdown Extra 1.1b1

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

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/

Hi All. I've just started using Markdown for my blog. So far it seems quite nice, but the one issue I've run into is a lack of "native" support for footnotes. I think that Daring Fireball's footnote style makes a lot of sense, and that's what I intend to use. However, it is a bit cumbersome to implement that style from within Markdown. I notice that the PHP

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

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.

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

This is a bug-fix release for PHP Markdown and PHP Markdown Extra. It's almost identical to version 1.0.2b8, minus the new features introduced in the 1.0.2 betas (shortcut links, markdown attribute support for plain PHP Markdown), plus a few minor improvements. You can download PHP Markdown & Extra from the project page: <http://www.michelf.com/projects/php-markdown/> Here

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

This is a mostly a bug-fix release. You can download it from here: <http://www.michelf.com/projects/php-markdown/> PHP Markdown 1.0.1e * Added support for internationalized domain names for email addresses in automatic link. Improved the speed at which email addresses are converted to entities. Thanks to Milian Wolff for his optimisations. * Made deterministic the conversion to

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

Here's another update to PHP Markdown and PHP Markdown Extra featuring some bug fixes. See the download link on the project's page: <http://michelf.com/projects/php-markdown/> This update also features a new emphasis parser which process regular and strong emphasis in one pass instead of two and four for previous versions of PHP Markdown and PHP Markdown Extra. The new parser

While we're talking about new syntax, I thought that I'd throw out an idea I had to extend the footnote syntax as it currently exists in PHP Markdown Extra. I'm not sure that it's the best way to solve this particular problem, but I figured I'd throw it out there to get any comments on it. It relates to the problem of specifying a document's GUID. A few months back,

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

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

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

from : benoit at transmekong.com to : markdown-discuss at six.pairlist.net Subj.: Use of Markdown Extra in a forum Date : Apr 19th 2007, 15:24:25 (GMT+7) Dear all, I have tried to implement PHP Markdown Extra in a forum (PunBB) and found that however well each message is translated, there are collisions when different messages in the same page have the same inside link names (footnotes, title

Hi, I have written my own implementation of markdown in Scala. I only later realized there is already one ( <http://tristanhunt.com/projects/knockoff/> ), but I put quite some work into mine and I think it is never bad to have alternatives, so I wanted to release it anyway. I want to use the same BSD License as the original markdown, but before I put it out into the wild I wanted to ask

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