similar to: What is the most recent offical test suite ?

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

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

Hi! I wrote an markdown interpreter in C. It should support most of the features markdown.pl has (hopefully). Please report any bugs. It would be a good idea if you could test the interpreter with you're own documents and report any differences to markdown.pl Mercurial: hg clone http://s01.de/~gottox/hg/cmarkdown/ Tarball: http://s01.de/~gottox/files/cmarkdown-0.3.tar.gz regards Gottox

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'm using Michel Fortin's MDTest cases to rewrite my html2text.php script. Just now I stumbled upon this bug (in PHP Markdown at least): # Input: Backtick: ``\``` # Output: <p>Backtick: ``&#96;``</p> # Should-Be Output: <p>Backtick: <code>`</code></p> If you (Michel) are already aware of this, just ignore me ;-) -- Milian Wolff

Hello, What should the following input produce? Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling with <g> and thus at least a visual similarity to German; English and Frisian have shifted g to [j] before palatal vowels The Dingus says: <p>Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling

PHP Markdown v 1.0.1i and PHP Markdown Extra v 1.1.5 generate invalid HTML for code blocks Take this input: paragraph codeblock Markdown will generate: <p>paragraph</p> <pre><code>codeblock </pre></code> Notice the wrong position of the closing code tag. -- Milian Wolff http://milianw.de

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

I'v encountered what seems to be a bug in PHP Markdown v1.0.1k. Given a UTF-8 with a BOM, the first line is not parsed. A brief search revealed a bug report for a similar issue in python- markdown: > I'm using the markdown.py command to generate HTML from Markdown > documentation and I've found that if a utf-8 file starts with a BOM > a paragraph is generated

Take the following input and both `Markdown.pl` and PHP Markdown will fail: ~~~Input~~~~~~ Codeblock ~~~End~~~~~~~ ~~~Expected~~~~ <pre><code> Codeblock</pre></code> ~~~End~~~~~~~ ~~~Actual Result~~ <p>Codeblock</p> ~~~End~~~~~~~~ There is already a testcase in MDTest for codeblocks in the first line, though the above is still not handled properly! --

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

Hi, First of all, thanks to John Gruber for the fantastic Markdown syntax and parse/render system. Also, thanks to Michel Fortin for his PHP 4 version of Markdown. Based on those two works, I have completed a **plugin-aware** PHP 5 version of Markdown. You can see it in Subversion here: * <http://solarphp.com/svn/trunk/Solar/Markdown.php> *

I hope this is not by design and not an already discussed bug. Take the following input: <hr id="foo" /> <hr id="foo"> <hr id="foo"/> <hr id="foo" /> <hr id="foo"> <hr id="foo"/> If this is run through Markdown a paragraph will wrap hr's numer 4-6. This behaviour

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/*"

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

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

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;

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

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