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.
On Tue, Sep 22, 2009 at 12:42 PM, Jerry Krinock <jerry at ieee.org> 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 <pre>, <code>, <script> blocks, etc. -- provided they exist in the input, which they likely won't until after a Markdown transform. LQ