I just noticed an issue with BlogCFC and Live Writer 2009. If you read my blog at all, you may have noticed I use the em dash a ton. For some reason I'm drawn to using the em dashes and ellipses.
Anyway, I just noticed that Live Writer does not translate the em dash character to an HTML entity (—), but instead posts it as a character code. This would be all fine and dandy, but there seems to be an issue posting this character as UTF-8—which is the default character coding for Writer 2009.
The fix is to Blogs > Edit blog settings... > Advanced and changed the Character Set to "Western European (Windows): Windows-1252" from the "Default (UTF-8)" setting.

I'm not sure if this issue goes away if you use the HTML markup type, but I prefer the cleaner XHTML (and it works better with my BlogCFC modded XMLRPC script.
I'd prefer to keep using UTF-8, but until I can figure out how to fix the weird UTF-8 encoding issues, I'm sticking with this decoding.
Last week I upgraded my dev system to a Dell Studio XPS-121M--which comes equipped with Windows Vista 64-bit. For the most part, I had no problems getting my software migrated over to the new box. However, for the first time I went to edit a CSS file this morning in Eclipse and was getting a blank screen.
I'm currently using the Aptana plug-in under Eclipse 3.3 (Europa) and thought something was wrong with my installation (since it was just a copy of the old directory.) After trying a number of things, I came across an open ticket at Aptana that indicates there's a problem with the Mozilla XUL support under Vista 64-bit.
NOTE:The full Aptana Studio was based on Eclipse v3.2 up until Studio v1.3. If you are running an old version of Aptana Studio, you may run into the same issue under Windows Vista 64-bit editions.
To resolve the problem, two fixes mentioned in the ticket worked for me:
Since I don't use the Preview mode (although I suppose that might be handy at times) I just disabled the Firefox support. This seems to be working well for the time being.
The good news is this apparently is fixed in Eclipse v3.4 (Ganymede.) However, last week when I was trying to get things up and running I was having problems connecting to the Eclipse update site, so I'm still on v3.3 for the time being. I'll try upgrading again to v3.4 maybe this weekend.
In the meantime, hopefully this helps someone out.