<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Conal Elliott &#187; Markdown</title>
	<atom:link href="http://conal.net/blog/tag/markdown/feed/" rel="self" type="application/rss+xml" />
	<link>http://conal.net/blog</link>
	<description>Inspirations &#38; experiments, mainly about denotational programming in Haskell</description>
	<lastBuildDate>Fri, 30 Jul 2010 02:56:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Switching blog engines</title>
		<link>http://conal.net/blog/posts/switching-blog-engines/</link>
		<comments>http://conal.net/blog/posts/switching-blog-engines/#comments</comments>
		<pubDate>Tue, 15 Jan 2008 23:46:55 +0000</pubDate>
		<dc:creator>conal</dc:creator>
				<category><![CDATA[Functional programming]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[GeSHi]]></category>
		<category><![CDATA[Markdown]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://conal.net/blog/2008-01/switching-blog-engines</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>I gave up on Blogger, where I&#8217;d been keeping my <a href="http://conal-elliott.blogspot.com">technical blog</a>.  Blogger was removing one leading space per line of pre-formatted html (&#8220;code&#8221;) on every edit/preview cycle.</p>

<p>Meanwhile, I&#8217;ve been enjoying using <a href="http://daringfireball.net/projects/markdown">Markdown</a>, so I poked aroud and found a <a href="http://wordpress">WordPress</a> solution I think I&#8217;ll like for a while.  You&#8217;re looking at it.</p>

<p>The steps are described in a post on <a href="http://www.dougalstanton.net/blog/index.php/2007/12/15/syntax-highlighting-with-markdown-in-wordpress">Syntax highlighting with Markdown in WordPress</a>.  It uses a combination of <a href="http://michelf.com/projects/php-markdown/extra">PHP Markdown Extra</a> and <a href="http://qbnz.com/highlighter">GeSHi</a> (Generic Syntax Highlighter), plus a small extension to specify which language for a block of code.  It works great.  I tweaked the PHP code to make the default language be Haskell instead of txt.  The GeSHi-decorated code even has links to library documentation, which I love.</p>

<p>I had a bit of trouble along the way and got help on the <code>#wordpress</code> IRC channel.  It turned out that I hadn&#8217;t followed the installation directions for PHP Markdown Extra, which say to move markdown.php out of its directory directly into my plugins directory.  Once I knew to look in the Apache error log, it was pretty easy to track down the problem.</p>

<p>Still to do:</p>

<ul>
<li>Work out how to automatically add documentation links to <a href="http://qbnz.com/highlighter">GeSHi</a>.  For now, I&#8217;ve manually added <code>Data.Monoid</code>, <code>Control.Applicative</code>, and <code>Control.Arrow</code>.</li>
<li>When I want to go public, get <a href="http://planet.haskell.org">Haskell Planet</a> to point to the new blog.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://conal.net/blog/posts/switching-blog-engines/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
