similar to: Babelmark

Hi, I've built a quick-and-dirty diff GUI for Babelmark (thanks, Michel!). You can get it as a bookmarklet here: http://attacklab.net/babelmark/ If either Michel or Tom is interested in hosting this, I'll be happy to do the grunt work for a real integration. It's kind of pain in the ass to hit the bookmarklet every time you get new data from the server. I've tested this

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

I'm curious how people think the following *should* be interpreted: - one 2. two http://babelmark.bobtfish.net/?markdown=-++one%0D%0A2.+two%0D%0A%0D%0A As you can see, implementations split into three groups here: (a) treat as an unordered list Markdown.pl, Python markdown, MultiMarkdown, BlueCloth, MarkdownJ, Showdown (b) treat as an unordered list with an ordered

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

Consider this code span: `grep ' '`. All implementations listed on [babelmark](http://babelmark.bobtfish.net) just simply wrap it as: <code>grep ' '</code> Viewed in browsers, the above code is equivalent to: <code>grep ' '</code> I think spaces should be preserved in code span,which maintains consistence with code block. For

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

Hi, I'm in the process of adding support for Markdown to a minimal CMS in Rails, [Railfrog][railfrog], which uses mime types to select appropriate processing. I have had a look through the archives but have not been able to see that a consensus has emerged as to what such a mime type for Markdown should look like. My reading of the RFCs suggests that it should be within the "text/*"

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 Everyone, Can someone spot the error in the following snippet of link text? It doesn't work through php-markdown in wordpress and I just wanted to know if there's something obvious I'm missing. Thanks in advance! can come of us. "Every good and perfect gift comes from above" ([James

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

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

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

Happy new year! This is the revised revised proposal: http://maruku.rubyforge.org/proposal.md http://maruku.rubyforge.org/proposal.html http://maruku.rubyforge.org/proposal.pdf I wait for comments. -- Andrea Censi "Life is too important to be taken seriously" (Oscar Wilde) Web: http://www.dis.uniroma1.it/~censi

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

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 got a problem with UL followed by by OL when I using perl module "Text-Markdown-1.0.5". I wrote the following markdown code. - a - b 1. 1 2. 2 I expected that Text-Markdown would produce the following HTML. <ul> <li>a</li> <li>b</li> </ul> <ol> <li>1</li> <li>2</li> </ol> However, "Text-Markdown-1.0.5"

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

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