jerakeen.org

by Tom Insam

notes☴

code☷

links☲

photos☵

Moving Past BlueCloth

Moving Past BlueCloth

created 01 May 2009 in links tagged bluecloth and markdown.

BlueCloth (the normal ruby markdown implementation) is slow. This is apparently much faster. Not that I care right now, I care much more about consistency of implementation, and the these seem to win there as well. Also, BabyShitGreenCloth is funny. Via Ash.

http://tomayko.com/writings/ruby-markdown-libraries-real-...

Showdown - Markdown in Javascript

Showdown - Markdown in Javascript

created 01 March 2007 in links tagged javascript and markdown.

ooooh, markdown in JavaScript. It works in Zimki, too, on the server side. Nifty.

http://www.attacklab.net/showdown-gui.html

My Wandering Wiki: MultiMarkdown

My Wandering Wiki: MultiMarkdown

created 19 September 2006 in links tagged markdown and markup.

Extended Markdown parser, does footnotes again (different syntax) and tables this time

http://fletcher.freeshell.org/wiki/MultiMarkdown

John MacFarlane - Pandoc

John MacFarlane - Pandoc

created 19 September 2006 in links tagged haskell, latex, markdown and markup.

Impressively close to my Grail, this will convert Markdown syntax (with a few changes) into HTML, latex, RTF, S5. Lovely. The footnote syntax is a little icky, though.

http://sophos.berkeley.edu/macfarlane/pandoc.html

rephrase § Markdown Footnotes

rephrase § Markdown Footnotes

created 19 September 2006 in links tagged footnotes, markdown, markup, syntax and text.

Markdown needs a footnotes syntax. This is an implementation of a possible method, discussed on the markdown mailing list last year.

http://rephrase.net/box/word/footnotes/

Python Implementation of Markdown

Python Implementation of Markdown

created 12 March 2006 in links tagged markdown and python.

http://www.freewisdom.org/projects/python-markdown/

Excerpts and Markdown

created 29 March 2005 in blog tagged markdown and text.

Markdown allows you to specify links [like this][1], and then specify the link target later in the file:

[1]: http://server/path/somewhere

This is really nice, and makes for very readable raw text, but it has a disadvantage when WordPress decides that it wants to automatically make an excerpt of something by truncating the raw text, then running it through the filter. You get a very ugly excerpt and lots of hanging links. The alternative, of course, is to process the text, produce XHTML, and then truncate it randomly, producing (probably) malformed XML. Not nice.

As a work-around, I’ve just removed all excerpts from this site - everything that ever appears should be full-text. It’s not like I type a lot normally…