<?xml version="1.0"?><rss version="2.0"><channel>   <title>Zappatic.net Blog feed</title>   <link>http://zappatic.net</link>   <description>The Zappatic.net Weblog Feed</description><item>   <title>SafariTidy becomes Safari Validator !</title>   <link>http://zappatic.net/blog/item/6/SafariTidy_becomes_Safari_Validator__</link>   <guid>http://zappatic.net/blog/item/6/SafariTidy_becomes_Safari_Validator__</guid>   <description>&lt;p&gt;
I&apos;ve rewritten the plugin to make use of the new extension mechanism in Safari 5. This means that the reliance on SIMBL is gone, and no private API&apos;s are used. Now it is just a webplugin-safari extension combination. The extension handles all the user interface, and the webplugin handles the actual validation. 
&lt;/p&gt;

&lt;p&gt;
Installation is pretty simple: copy the webplugin to ~/Library/Internet Plug-Ins, and double click the safariextz file. The latter requires you having enabled extensions in Safari. To do this, open the preferences, and go to the &apos;Advanced&apos;-pane. Check &apos;Show Develop menu in menu bar&apos;. In the newly visible &apos;Develop&apos;-menu, select &apos;Enable Extensions&apos;.
&lt;/p&gt;

&lt;p&gt;
Please note that the W3C validation takes time! It will slow your browsing down, especially if the site contains a lot of (i)frames. Just go to the preferences, and disable the W3C validation.
&lt;/p&gt;

&lt;p&gt;
HTML5 support isn&apos;t there yet, as I&apos;m still investigating the best solution. The validator.nu engine (which W3C uses) assumes you will be running it as a webservice, which is not ideal in a browser situation. Opening a port and running a server in the browser is definitely a worst case solution.
&lt;/p&gt;</description>   <pubDate>Thu, 10 Jun 2010 22:03:56 +0200</pubDate></item></channel></rss>