As you can see the conversion to Subtext is complete.  All in all it was fairly simple and went as smooth as I could have hoped.

I haven't looked at any source code but I'm impressed with the functionality and how well it works out of the box.  It needs a little polish, but it's an impressive app for a zero dot something build.  My hat is off to the Subtext team, I think you've put together a nice app.

There is this one dig I have to make, however.  I switched from Wordpress 2.0 and there is no "simple" way to convert the data.  I did search the Subtext forums on Sourceforge and found a thrown-together app to export Wordpress data to BlogML format for importing using the built-in Subtext import feature.  I understand it would be difficult if not impossible to create and maintain converters for every other blog platform out there.

So, I'm working on a Wordpress to Subtext direct convert app.  So far, it's been pretty simple.  The data structures map fairly nicely.  My hope is to make it available by this weekend as a simple Windows app to do straight MySQL to SQL data conversions, skipping the XML export.  From there I'd like to make it flexible enough to support multiple versions of Wordpress, and from there I'd like to add a feature for advanced users to drag-and-drop map the data structures if the app can't figure them out.

Why all this work for a simple one-time-use converter?  I dunno.  Something to keep me occupied and fiddling around with non work-related code.

The last thing I'll say about it is that I'm posting this from Firefox 2.0 on my Mac.  It works fine in Safari with the exception of the HTML editor.  Mac functionality is one of the main reasons I chose it over dasBlog - sorry Hanselman dasBlog looks terrible in Safari.  Other than that it's a peach in FF.

Cheers.