Comments on: Drupal Markdown plugin progress… http://amit.chakradeo.net/2004/05/28/drupal-markdown-plugin-progress/ Stay Hungry. Stay Foolish! Thu, 11 Mar 2010 06:10:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: noah http://amit.chakradeo.net/2004/05/28/drupal-markdown-plugin-progress/comment-page-1/#comment-4 noah Thu, 01 Jan 1970 00:00:00 +0000 /wordpress/2004/05/28/drupal-markdown-plugin-progress/#comment-4 More Markdown, please! Any chance you could roll SmartyPants in with it, too? In fact, wouldn't it make more sense to look into finding a way to execute a Perl filter as a Drupal module? Because if it could be done, then you never have to worry about losing parity with the real Markdown release... and it IS just a filter after all... More Markdown, please! Any chance you could roll SmartyPants in with it, too?

In fact, wouldn’t it make more sense to look into finding a way to execute a Perl filter as a Drupal module? Because if it could be done, then you never have to worry about losing parity with the real Markdown release… and it IS just a filter after all…

]]> By: noah http://amit.chakradeo.net/2004/05/28/drupal-markdown-plugin-progress/comment-page-1/#comment-5 noah Thu, 01 Jan 1970 00:00:00 +0000 /wordpress/2004/05/28/drupal-markdown-plugin-progress/#comment-5 "Some people have a concern for lock-in into a particular text format." Kind of a silly concern, because you're always locked into something... as long as it's structured you can always convert out of it later if you have to. So I eventually patched out the filter to add support for SmartyPants-PHP (so it's like "Markdown with SmartyPants" when using MovableType) and made it a pure filter. I believe John Gruber said it himself that one of the design points of Markdown was that it would leave existing HTML alone, so why the need to choose? Wiki.module doesn't make this version-number/on-or-off distinction so why was this in Markdown.module? It seems like if you really want to specify between HTML or Markdown, it should be an extension of Type (i.e. "HTML/text or PHP" as in some nodes). Don't you think? “Some people have a concern for lock-in into a particular text format.”

Kind of a silly concern, because you’re always locked into something… as long as it’s structured you can always convert out of it later if you have to.

So I eventually patched out the filter to add support for SmartyPants-PHP (so it’s like “Markdown with SmartyPants” when using MovableType) and made it a pure filter.

I believe John Gruber said it himself that one of the design points of Markdown was that it would leave existing HTML alone, so why the need to choose? Wiki.module doesn’t make this version-number/on-or-off distinction so why was this in Markdown.module?

It seems like if you really want to specify between HTML or Markdown, it should be an extension of Type (i.e. “HTML/text or PHP” as in some nodes). Don’t you think?

]]>