I write and think better when I don’t have to think a lot about markup. I know that means my writing lacks machine-readable semantic depth, but I’m happy with that and it’s not really the theme of this post, but I’ll bite… a little.

To be fair to WLW, the ink blogging component is a 3rd-party plugin that simply takes the ink format and renders it as an image when published on a blog. Missing alt-text is the plugin’s fault. The original ink is preserved in the WLW plugin so it can be edited and republished from the ink format. The ongoing usefulness of inkblog content is questionable, but it is fast and convenient — things markup zealots should target for immediate elimination ;) Regular images have a generous complement of standard markup to mess with.

The space pairs are due to my 28 year-old reflex and preference for two-spaces-after-punctuation. The non-breaking spaces are generated to preserve the intended formatting when you insert two spaces instead of one after a period. This appears to be common practice for achieving double spaces in HTML. The 160’s don’t turn up when you type, like, proper sentences.

As you’d expect, WLW also provides direct access to the markup so you can manicure before publication, but I haven’t found any unexplainable markup atrocities yet.

The markup is not as bad as some atrocities committed by Microsoft products. But what’s with the  s at the end of the sentences? A no-break space followed by a space, WTF?

Where’s the alt tag on the image? In what way is this “ink” as opposed to any old hand-drawn image?

Yes I am being kinda picky. (Not a Microsoft or a WYWIGYW fanboy, obviously…)