, for example).

There may be abusable code in projects like ELinks.

http://en.wikipedia.org/wiki/ELinks

LQ

From jgm at berkeley.edu  Fri Sep 11 23:30:44 2009
From: jgm at berkeley.edu (John MacFarlane)
Date: Fri, 11 Sep 2009 20:30:44 -0700
Subject: lunamark - markdown in lua using a PEG grammar
Message-ID: <20090912033043.GA1240@protagoras.phil.berkeley.edu>

Markersdown:

I was fooling around with lua and decided to write a markdown parser
using the terrific lpeg library.  Here's the result:
http://github.com/jgm/lunamark/tree/master

There are already two markdown libraries for lua, one a native lua
implementation based on global substitutions, the other a binding
to discount.  What makes lunamark different is that it is based
on a PEG grammar (adapted from my peg-markdown).  This can be found
in the file lunamark/markdown_parser.lua in the source tree.

Lunamark converts standard markdown to HTML and LaTeX.  Adding
a new output format is easy (the LaTeX writer took about 20 minutes
to add).  It is also possible to add new input formats.

Lunamark passes the Markdown 1.0.3 test suite (except for one edge
case involving loose/tight lists, and here its behavior is consistent
with the markdown syntax description -- see the README for peg-markdown
for discussion).

As for performance, lunamark is about the same speed as PHP Markdown in
my tests.

John

From qaramazov at gmail.com  Sat Sep 12 03:20:48 2009
From: qaramazov at gmail.com (Yuri Takhteyev)
Date: Sat, 12 Sep 2009 03:20:48 -0400
Subject: lunamark - markdown in lua using a PEG grammar
In-Reply-To: <20090912033043.GA1240@protagoras.phil.berkeley.edu>
References: <20090912033043.GA1240@protagoras.phil.berkeley.edu>
Message-ID: 

> As for performance, lunamark is about the same speed as PHP Markdown in
> my tests.

Is this with or without counting the time necessary to read the input?
On my test, reading a wiki page of 500 words _once_ and then
converting it 1000 times, lunamark is actually about 2.5 times faster
than PHP Markdown.

But perhaps a comparison with the other two Lua options is more
relevant. On the same benchmark, lunamark is 5-6 times faster than
markdown.lua and 12-13 times slower than lua-discount. (Of course,
lua-discount is basically a binding to a C implementation.)

- yuri

From jgm at berkeley.edu  Sat Sep 12 13:25:02 2009
From: jgm at berkeley.edu (John MacFarlane)
Date: Sat, 12 Sep 2009 10:25:02 -0700
Subject: lunamark - markdown in lua using a PEG grammar
In-Reply-To: 
References: <20090912033043.GA1240@protagoras.phil.berkeley.edu>

Message-ID: <20090912172502.GC7239@protagoras.phil.berkeley.edu>

+++ Yuri Takhteyev [Sep 12 09 03:20 ]:
> > As for performance, lunamark is about the same speed as PHP Markdown in
> > my tests.
> 
> Is this with or without counting the time necessary to read the input?
> On my test, reading a wiki page of 500 words _once_ and then
> converting it 1000 times, lunamark is actually about 2.5 times faster
> than PHP Markdown.

That's nice to hear. My tests included reading the input, and also
expanding tabs, since PHP markdown does that. (But lunamark can
handle input with unexpanded tabs, so expanding tabs is not really
necessary.)

> But perhaps a comparison with the other two Lua options is more
> relevant. On the same benchmark, lunamark is 5-6 times faster than
> markdown.lua and 12-13 times slower than lua-discount. (Of course,
> lua-discount is basically a binding to a C implementation.)

That's about what I found too.  discount is incredibly fast.
But the lunamark code is about 10x shorter, and should be easier
to extend and revise.  It is also very portable, since both lua
and the lpeg library are written in ANSI C. So it might be useful for
some people.

John

From jerry at ieee.org  Tue Sep 22 12:42:00 2009
From: jerry at ieee.org (Jerry Krinock)
Date: Tue, 22 Sep 2009 09:42:00 -0700
Subject: Scripting: Invoke Markdown *before* SmartyPants
Message-ID: <9B8A258A-6C11-4CD6-833B-5A9BB0BA0779@ieee.org>

I could not find anywhere in John Gruber's documentation the  
recommended order of Markdown vs. SmartyPants in a scripted process.   
I guessed SmartyPants first, and that worked until I tried to encode a  
link with a title like this:

    An [example](http://url.com/ "Title")

SmartyPants encoded the quotes, which created a mess.

So, I changed the order to process text through Markdown first, then  
SmartyPants.  So far, so good.

From public at quillio.com  Tue Sep 22 13:16:57 2009
From: public at quillio.com (Lou Quillio)
Date: Tue, 22 Sep 2009 13:16:57 -0400
Subject: Scripting: Invoke Markdown *before* SmartyPants
In-Reply-To: <9B8A258A-6C11-4CD6-833B-5A9BB0BA0779@ieee.org>
References: <9B8A258A-6C11-4CD6-833B-5A9BB0BA0779@ieee.org>
Message-ID: 

On Tue, Sep 22, 2009 at 12:42 PM, Jerry Krinock  wrote:
> So, I changed the order to process text through Markdown first, then
> SmartyPants. ?So far, so good.

That's what you want. Also, Smartypants won't reach into ,
, 