<?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>BigSmoke &#187; GeSHi</title>
	<atom:link href="http://blog.bigsmoke.us/tag/geshi/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bigsmoke.us</link>
	<description>Smokes your problems, coughs fresh air.</description>
	<lastBuildDate>Sat, 04 Feb 2012 18:03:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Finding a decent GeSHi plugin for WordPress</title>
		<link>http://blog.bigsmoke.us/2009/04/13/wordpress-geshi-plugin</link>
		<comments>http://blog.bigsmoke.us/2009/04/13/wordpress-geshi-plugin#comments</comments>
		<pubDate>Mon, 13 Apr 2009 14:03:59 +0000</pubDate>
		<dc:creator>Rowan Rodrik</dc:creator>
				<category><![CDATA[BigSmoke.US]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[BBCode]]></category>
		<category><![CDATA[GeSHi]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=310</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>I like <a href="http://qbnz.com/highlighter/">GeSHi</a> (enough even to have written a <a href="http://geshi.svn.sourceforge.net/viewvc/geshi/trunk/geshi-1.0.X/src/geshi/bnf.php">language file</a> for it). For ages now, I&#8217;ve used a WordPress plugin by Dan Peverill. But for as long as I&#8217;ve been using the plugin, I&#8217;ve been looking to get rid of it.</p>

<p>Dan Peverill&#8217;s GeSHI plugin sucks for two reasons:</p>
<ol>
  <li>It&#8217;s no longer being maintained. It doesn&#8217;t even seem to justify a page on Dan&#8217;s website anymore (for which reason I&#8217;m not going to give him any link-juice).</li>
  <li>It breaks HTML. With the plugin enabled I can no longer use the <tt>&lt;code&gt;</tt> tag to mark in-line elements as being <em>code</em>. Frankly, this is annoying and I find myself typing <tt>&lt;tt&gt;</tt> often when I mean <tt>&lt;code&gt;</tt>.</li>
</ol>

<p>A search for <a href="http://wordpress.org/extend/plugins/tags/geshi">WordPress plugins tagged <q>GeSHi</q></a> reveals a number of results:  <a href="http://wordpress.org/extend/plugins/sniplets/">Sniplets</a>, <a href="http://wordpress.org/extend/plugins/codecolorer/">CodeColorer</a>, <a href="http://wordpress.org/extend/plugins/devformatter/">Developer Formatter</a>, and <a href="http://wordpress.org/extend/plugins/wp-synhighlight/">WP-SynHighlight</a>. <a href="http://wordpress.org/extend/plugins/wp-syntax/">WP-Syntax</a> is a plugin that is missing from the tag search.</p>

<p><strong>Sniplets</strong> seems much too generic to my taste. I just want a GeSHi highlighter, period.</p>

<p><strong>CodeColorer</strong> says it does what I want, but if I ever want to use the TinyMCE editor again, I won&#8217;t be able to with this plugin. Shouldn&#8217;t be too much of a problem, but still&#8230;</p>

<p><strong>Developer Formatter</strong> is very thoroughly written and even sports a TinyMCE plug-in for copying/pasting the code. It is pretty big, though, and, as a rule, I tend to avoid plug-ins that complicate the database schema. I also don&#8217;t really see how these extra tables are an advantage feature-wise.</p>

<p><strong>WP-SynHighlight</strong> uses a custom BBCode-style tag, <tt>&#x5B;codesyntax]</tt> I like this (if you&#8217;re going to use pointy brackets, at least keep out of the HTML namespace), though I don&#8217;t like the attempt at a generic name; what&#8217;s wrong with calling the tag <tt>[geshi]</tt>? Seriously&#8230; I&#8217;m sure I&#8217;m going to forget this name billions of times if I&#8217;ll use this plug-in.</p>

<p><strong>WP-Syntax</strong> uses the <tt>&lt;pre&gt;</tt> tag with a few custom attributes. This at least is better than the <strong>officially inline</strong> <tt>&lt;code&gt;</tt> tag that my current plugin uses, because most of the time that I&#8217;d use a <tt>&lt;pre&gt;</tt> tag I really do want syntax highlighting. Just wondering: will it also allow my to use it normally for that other rare occasion? Sadly, the plugin <em>will</em> doubtlessly wreak havoc with the visual (TinyMCE) editor.</p>

<p>So, which plugin will I choose? I am somehow inclined to want a plugin that <em>can</em> play nice with the visual editor because I keep telling myself how much nicer it would be to switch to the visual editor for all my posting. (That this will be difficult because I disabled WP&#8217;s &#8216;<tt>wpautop</tt>&#8216; filter to rid myself of its eagerness is a story for some later time.) This requirement rules out CodeColorer and WP-Syntax.</p>

<p>That leaves Developer Formatter and WP-SynHighlight. Both seem to fit my purpose. Developer Formatter sports a nice TinyMCE plugin for inserting code, but I don&#8217;t think that switching to TinyMCE will suddenly and unexpectedly make me afraid of typing. Besides, I really don&#8217;t want the extra tables in my database without a very good reason, so, for now, I will try <a href="http://wordpress.org/extend/plugins/wp-synhighlight/">WP-SynHighlight</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://blog.bigsmoke.us/2009/04/13/wordpress-geshi-plugin/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

