<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MarsEdit Markdown</title>
	<atom:link href="http://www.red-sweater.com/blog/324/marsedit-markdown/feed" rel="self" type="application/rss+xml" />
	<link>http://www.red-sweater.com/blog/324/marsedit-markdown</link>
	<description>Mac &#38; Technology Writings by Daniel Jalkut</description>
	<lastBuildDate>Wed, 18 Jan 2012 18:10:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Michel Fortin</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-98022</link>
		<dc:creator>Michel Fortin</dc:creator>
		<pubDate>Mon, 14 May 2007 18:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-98022</guid>
		<description>&quot;if one instance of Perl can simply have scripts run through it repeatedly, that solves the issue.&quot;

I&#039;m not sure that&#039;s possible in the way you suggest it. What you can do is run a custom-made Perl script that calls the Markdown function for you without ending itself at the end. When you send some input, it convert the text and send back the result... and then wait for the next input before calling again the Markdown function.

I&#039;ve made such a script in PHP for PHP Markdown (about 15 lines of code). I don&#039;t have any C or Objective-C code to go along however. If you&#039;re interested, drop me an email.</description>
		<content:encoded><![CDATA[<p>&#8220;if one instance of Perl can simply have scripts run through it repeatedly, that solves the issue.&#8221;</p>
<p>I&#8217;m not sure that&#8217;s possible in the way you suggest it. What you can do is run a custom-made Perl script that calls the Markdown function for you without ending itself at the end. When you send some input, it convert the text and send back the result&#8230; and then wait for the next input before calling again the Markdown function.</p>
<p>I&#8217;ve made such a script in PHP for PHP Markdown (about 15 lines of code). I don&#8217;t have any C or Objective-C code to go along however. If you&#8217;re interested, drop me an email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Jalkut</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-97528</link>
		<dc:creator>Daniel Jalkut</dc:creator>
		<pubDate>Sun, 13 May 2007 15:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-97528</guid>
		<description>Cool Michel, that&#039;s a great idea. I had been wondering whether there was some way to set up a perl &quot;runtime&quot; in memory, but of course if one instance of Perl can simply have scripts run through it repeatedly, that solves the issue.

I will look into this when I next pick up the preview code.</description>
		<content:encoded><![CDATA[<p>Cool Michel, that&#8217;s a great idea. I had been wondering whether there was some way to set up a perl &#8220;runtime&#8221; in memory, but of course if one instance of Perl can simply have scripts run through it repeatedly, that solves the issue.</p>
<p>I will look into this when I next pick up the preview code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel Fortin</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-96649</link>
		<dc:creator>Michel Fortin</dc:creator>
		<pubDate>Fri, 11 May 2007 20:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-96649</guid>
		<description>Now that I think of it, you could probably speed up the live preview by not creating a new Perl process every time and instead having one that runs in background, idle until it recieve new input. I&#039;ve been doing some benchmarking with PHP Markdown and found out that processing most input generally takes less than 15 ms, but starting a new PHP process adds an overhead of about 100 ms (iBook G4; 1.2 Ghz). I believe these two numbers to be slightly higher for Perl.</description>
		<content:encoded><![CDATA[<p>Now that I think of it, you could probably speed up the live preview by not creating a new Perl process every time and instead having one that runs in background, idle until it recieve new input. I&#8217;ve been doing some benchmarking with PHP Markdown and found out that processing most input generally takes less than 15 ms, but starting a new PHP process adds an overhead of about 100 ms (iBook G4; 1.2 Ghz). I believe these two numbers to be slightly higher for Perl.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eduo</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85937</link>
		<dc:creator>Eduo</dc:creator>
		<pubDate>Fri, 20 Apr 2007 18:47:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85937</guid>
		<description>Cool. That probably means I&#039;ll stick with Markdown extra then as I have so far. :)</description>
		<content:encoded><![CDATA[<p>Cool. That probably means I&#8217;ll stick with Markdown extra then as I have so far. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel Fortin</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85880</link>
		<dc:creator>Michel Fortin</dc:creator>
		<pubDate>Fri, 20 Apr 2007 15:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85880</guid>
		<description>About &quot;rel&quot; attributes for links, that&#039;s on my todo list for the next version of PHP Markdown Extra, with &quot;class&quot; and possibly other useful standard attributes (&quot;id&quot;, &quot;lang&quot;, &quot;hreflang&quot;, etc.).

I too would like to see things added to the official Markdown syntax. When I first released PHP Markdown Extra, what I had in mind was that features would slowly percolate to regular Markdown (with possible modifications) while the Extra version could keep an edge. It turns out that John Gruber&#039;s Markdown hasn&#039;t been updated much since then, even for bug fixes. That means PHP Markdown isn&#039;t evolving much either on the syntax side, although I&#039;ve fixed many bugs since the last release of John&#039;s Markdown, and changed the architecture to help build extensions on the top of it.

About creating an Objective-C version, that sounds like an interesting project. I&#039;m pretty sure I could do it, but it would take a lot of time, time I prefer to spend elsewhere at the moment.</description>
		<content:encoded><![CDATA[<p>About &#8220;rel&#8221; attributes for links, that&#8217;s on my todo list for the next version of PHP Markdown Extra, with &#8220;class&#8221; and possibly other useful standard attributes (&#8220;id&#8221;, &#8220;lang&#8221;, &#8220;hreflang&#8221;, etc.).</p>
<p>I too would like to see things added to the official Markdown syntax. When I first released PHP Markdown Extra, what I had in mind was that features would slowly percolate to regular Markdown (with possible modifications) while the Extra version could keep an edge. It turns out that John Gruber&#8217;s Markdown hasn&#8217;t been updated much since then, even for bug fixes. That means PHP Markdown isn&#8217;t evolving much either on the syntax side, although I&#8217;ve fixed many bugs since the last release of John&#8217;s Markdown, and changed the architecture to help build extensions on the top of it.</p>
<p>About creating an Objective-C version, that sounds like an interesting project. I&#8217;m pretty sure I could do it, but it would take a lot of time, time I prefer to spend elsewhere at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eduo</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85803</link>
		<dc:creator>eduo</dc:creator>
		<pubDate>Fri, 20 Apr 2007 08:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85803</guid>
		<description>Jochen: Y personally wouldn&#039;t mind seeing a new version of markdown (officially sanctioned by Gruber) with those additions and allowances for some extended markup or an official path of extensions at least.

As it stands, where I write I have a need to specify &quot;rel=&quot; attributes in some links, as well as other extended attributes and specific classes from time to time.

I know the idea of Markdown is to avoid this, and I currently do this including it in html blocks that are then ignored.

I still think it would be nice to have the ability to do it all in markdown.</description>
		<content:encoded><![CDATA[<p>Jochen: Y personally wouldn&#8217;t mind seeing a new version of markdown (officially sanctioned by Gruber) with those additions and allowances for some extended markup or an official path of extensions at least.</p>
<p>As it stands, where I write I have a need to specify &#8220;rel=&#8221; attributes in some links, as well as other extended attributes and specific classes from time to time.</p>
<p>I know the idea of Markdown is to avoid this, and I currently do this including it in html blocks that are then ignored.</p>
<p>I still think it would be nice to have the ability to do it all in markdown.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jochen Wolters</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85797</link>
		<dc:creator>Jochen Wolters</dc:creator>
		<pubDate>Fri, 20 Apr 2007 07:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85797</guid>
		<description>Markdown is awesome. I have to write &quot;real HTML&quot; for one blog I post to, while allowing myself ;) to use Markdown on my own site, and Markdown is so much more enjoyable to write in because it requires _much_ less effort.

I just wish that the extensions that Michel Fortin built into his excellent &lt;a href=&quot;http://www.michelf.com/projects/php-markdown/extra/&quot; rel=&quot;nofollow&quot;&gt;Markdown Extra plug-in&lt;/a&gt; would find their way into John Gruber&#039;s &quot;official&quot; implementation.</description>
		<content:encoded><![CDATA[<p>Markdown is awesome. I have to write &#8220;real HTML&#8221; for one blog I post to, while allowing myself ;) to use Markdown on my own site, and Markdown is so much more enjoyable to write in because it requires _much_ less effort.</p>
<p>I just wish that the extensions that Michel Fortin built into his excellent <a href="http://www.michelf.com/projects/php-markdown/extra/" rel="nofollow">Markdown Extra plug-in</a> would find their way into John Gruber&#8217;s &#8220;official&#8221; implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eduo</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85618</link>
		<dc:creator>eduo</dc:creator>
		<pubDate>Thu, 19 Apr 2007 15:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85618</guid>
		<description>Ryan: You are right. I probably think of Markdown as intuitive because it reminds me the way I used to emphasize, underline, mark as headings, etc. back in 1992 in usenet  (I think ETEXT documents use a similar format as well).

To me nowadays it&#039;s almost natural to emphasize using underscores, REALLY emphasize using asterisks, make lists using dashes, mark headings with lines of dashes or equal signs below the heading, etc. That may be the reason I see it as intuitive.</description>
		<content:encoded><![CDATA[<p>Ryan: You are right. I probably think of Markdown as intuitive because it reminds me the way I used to emphasize, underline, mark as headings, etc. back in 1992 in usenet  (I think ETEXT documents use a similar format as well).</p>
<p>To me nowadays it&#8217;s almost natural to emphasize using underscores, REALLY emphasize using asterisks, make lists using dashes, mark headings with lines of dashes or equal signs below the heading, etc. That may be the reason I see it as intuitive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Harrell</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85614</link>
		<dc:creator>Jeff Harrell</dc:creator>
		<pubDate>Thu, 19 Apr 2007 15:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85614</guid>
		<description>You can mix Markdown and HTML, easily. The specifics vary depending on whether you&#039;re using the Perl version or the PHP version (Movable Type versus WordPress, in wildly oversimplified blog terms), but in general, Markdown ignores block-level HTML elements. You can mix and match inline HTML elements to your heart&#039;s content -- using Markdown syntax to italicize words inside an HTML link, for example -- but Markdown ignores everything inside an HTML div or paragraph element.</description>
		<content:encoded><![CDATA[<p>You can mix Markdown and HTML, easily. The specifics vary depending on whether you&#8217;re using the Perl version or the PHP version (Movable Type versus WordPress, in wildly oversimplified blog terms), but in general, Markdown ignores block-level HTML elements. You can mix and match inline HTML elements to your heart&#8217;s content &#8212; using Markdown syntax to italicize words inside an HTML link, for example &#8212; but Markdown ignores everything inside an HTML div or paragraph element.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Ballantyne</title>
		<link>http://www.red-sweater.com/blog/324/marsedit-markdown/comment-page-1#comment-85613</link>
		<dc:creator>Ryan Ballantyne</dc:creator>
		<pubDate>Thu, 19 Apr 2007 15:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/324/marsedit-markdown#comment-85613</guid>
		<description>Hmm...interesting concept. But I&#039;m a control freak when it comes to marking up web content, and I don&#039;t know if I would want to let a tool like Markdown handle it for me.

Unless...can you mix HTML and markdown in one? If I had the ability to drop into HTML for finer control of some elements while letting Markdown handle the ones that aren&#039;t so important, I might see a use for this.</description>
		<content:encoded><![CDATA[<p>Hmm&#8230;interesting concept. But I&#8217;m a control freak when it comes to marking up web content, and I don&#8217;t know if I would want to let a tool like Markdown handle it for me.</p>
<p>Unless&#8230;can you mix HTML and markdown in one? If I had the ability to drop into HTML for finer control of some elements while letting Markdown handle the ones that aren&#8217;t so important, I might see a use for this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

