qaramazov at gmail.com
Sat Mar 22 13:57:39 EDT 2008
This is a great tool. It won't solve all of our problems by itself
(we still need a spec), but I think it will help a great deal if we
want to try to bring all the implementations into agreement.
Some of my tests that show interesting differences:
<%foo ok %>: http://michelf.com/projects/babelmark/?markdown=%3C%25foo+ok+%25%3E
(BTW, where does one get Markdown.pl 1.0.2 beta? Markdown website
says that the last version is 1.0.1, of 2004.)
2-tier list indented by three spaces:
Now, on this one, I must say I have mixed feelings, since
python-markdown is the only implementation that follows "Markdown
Syntax" and treats the item indented by three spaces as being at the
same level. Makes me feel like a naive fool for following the "spec".
One more thing: python-markdown is a stickler for explicit encoding
(because we rely on it for bidi-detection). The input must be either
python Unicode object or UTF8 encoded byte-string or you must say what
encoding you are using. Your test doesn't seems to send something
other than UTF8 without specifying encoding.
Should we start a page on the wiki to collect those examples so that
we can then discuss what ought to be done in each case?
On Sat, Mar 22, 2008 at 10:09 AM, Michel Fortin
<michel.fortin at michelf.com> wrote:
> 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.
More information about the Markdown-Discuss