Windows Live Writer Beta 3 was recently announced and it works really well. That is to say, it “does what it says in the tin”. Writing well-formed blog posts is really simple, it even downloads styles directly from my WordPress blog and allows to me to do proper previews to see exactly what I will get before I publish a post, even when working offline.

There’s even more rich functionality and interoperability with third-party platforms than you might expect from a Microsoft product. For example, WordPress.com supports hierarchical categories. I find this especially useful as I show my categories as a drop-down list rather than take up loads of the sidebar with lots of choices. Windows Live Writer (WLW) provides me the ability to categorise posts, and to add new categories if I need them, including specifying a parent category so they fit into the multi-level hierarchy. Oh, and it does all this offline as well. This is great, and it’s the sort of attention to detail which I appreciate being in a product I use several times a week.

And now the Bad News: WLW does not support the new WordPress Tags by default

WordPress.com have announced a change to the way they use categories and tags. Windows Live Writer Beta 3 was released before this change and does not know what to do with them, so it does not create any, and removes any that already exist if you edit a previous post. However, there is a way to fix this with a registry change, but I found it caused some instability.

What is the point of Tags?

Basically lots of people would create categories to use just once, in the way that they might use tags or keywords on other platforms in order to provide good search engine terms and attract traffic. However, this has a couple of problems. Firstly because categories are universal throughout WordPress (if I happen to create a category with a name matching one that someone else used it shows a really low Category ID number, a uniquely named one would get a new, high number).

It also makes a real mess of people’s category lists as they end up really long and to some extent pointless – as a blog reader, I expect the idea of a category to mean a container which will have more than one post in. “Hey, they have a whole category of posts for Live Writer! Oh, just the one post” is always a disappointment. The category list can also give me an idea of the overall angle of the site – is this a web copywriter writing about a useful tool for editing blogs, or a developer who happens to use this tool and maybe writes extensions for it?

So, the new definitions on WordPress.com now line up with most other blogs – categories are permanent things you create to organise your posts into groups, tags are just transient things you use to describe what is in a particular post in such a way that people can search for them more easily, and over time they may form a sort of grouping by serendipity as you use the same tags over and over when writing about similar subjects.

Tag cloud widget for finding posts by tags

There is even a new widget to show a “Tag cloud” in the sidebar of some themes, as you will have seen on many other platforms before. This shows frequent tags in a larger, bolder format to indicate their repetition (on that particular blog) so one-offs appear much smaller and less obtrusively. There is also a limit of 45 tags shown at once, according to a thread in the support forums, which prevents it from getting too huge. I assume this means only the 45 most frequent tags will appear, not the first 45 used. When you hover over a tag name it shows in a tooltip how many posts are associated with that tag, which is useful.

Tag cloud issues

This “Tag cloud” widget does not work properly yet. Firstly, it seems to take an absolute age for it to update after publishing posts with new tags. I’ve been waiting over an hour now for a bunch of words to show up and they have not yet done so. This might be because of some system issues as loads of regular bloggers are probably updating loads of previous posts (as I am), but it remains to be seen whether this improves with time.

Secondly, the widget simply does not link properly to the related posts. The FAQ about the difference between tags and categories says this:

A post into the category ‘food’ and with the tag ‘rice’ will look like this:

http://faq.wordpress.com/category/food/

http://faq.wordpress.com/tag/rice/

Hovering over a link in the Tag cloud shows the URL correctly formed to use the tags such as http://veroblog.wordpress.com/tag/windows-live-writer/. However, when clicked this redirects to http://veroblog.wordpress.com/category/windows-live-writer/ which in this case does not exist.

What about Windows Live Writer and WordPress Tags?

Problem 1: There is nowhere in the GUI of WLW Beta 3 to add tags in.

Categories still work as expected, but there’s no way to actually add a tag in WLW as installed. Hopefully they will add this functionality by default to the live release. This is supposed to be the last Beta before the final code, unless this WordPress issue changes things and they decide a Beta 4 is needed to push this out.

Problem 2: WARNING! If you use WLW to edit an existing post which has tags, they are dropped when you re-publish

Let’s walk through this:

You write a new post in Windows Live Writer (or the web editing tool).
You then use the web interface to edit the post and add some tags.
You later edit it in WLW (which will download the post from your blog if you have edited it in the web interface since last touching it in WLW).
You make a change and republish.

Oops! Because you have no means to add tags, it now has none. It does not keep this metadata somewhere, untouched by your edit. It does not try to do a clever merge, it just replaces the post and all its metadata, categories etc wholesale. (Except it keeps the original posting date/time stamp). If you don’t make a change to WLW (see below) and you are adding tags in the web interface, expect to see thm disappear when you edit with WLW.

How to add a tags field to WLW to solve these problems

Actually, you can add a field for putting in tags (or keywords, as WLW calls them).

<edit:
Joe Cheng has published a tool to do this to save you from editing the registry directly. You can read about it and download from here.
Also, Joseph Scott has updated the manifest at WordPress.com to make it automatic so if you start WLW, close it again and restart you should get the new settings and the keyword field will be available to you without doing anything else.
Thanks to both guys for their contributions via the comments. The rest of the post remains for anyone that still wants to see it, although you should not need it given both options above. /edit>

You need to make a change to the registry, so make sure to close WLW, check that you have backups, permission from your parents, and you are not too drunk to do this safely. Don’t edit the registry if you are not sure what you are doing. This information is provided “as is”, I can’t help you if you break things by following this advice.

If you have a version before Beta 3, Windows Live Writer was a separate application, and the reg key you need will be here:

HKCU\Software\Windows Live Writer\Weblogs\{blog-id}\UserOptionOverrides

Beta 3 became part of the Windows Live Suite, so the path changes to:

HKCU\Software\Microsoft\Windows Live\Writer\Weblogs\{blog-id}\UserOptionOverrides

If you use WLW for editing multiple blogs, then go to each {blog-id} in turn and check the BlogName value for the one you want. Now you have the right one, under UserOptionOverrides you need to add a String “supportsKeywords” with a value of “yes”. Restart WLW.

To the right of the publish date at the bottom right hand corner is a double up-arrow. Click it and a box expands which gives you access to all the metadata for your post, and now the keywords tag is available for you to put a comma-separated list of tags into before you publish. This does solve the problems above, but I have found it makes WLW unstable in certain ways, such as trying to edit a draft which did not have tags associated with it, and even downloading a published post to make changes has been causing me some crashes in an otherwise very stable product. More testing required for me to pin down what combination causes a problem.

<edit2: I can now only reproduce the instability on one particular post (this one, as it happens), all others seem fine. /edit>

Share this post :

This is supposedly to be the last of the Beta versions of WLW before a final one is released. There are a few changes over Beta 2, most notably where the program gets installed.

More information about switching dictionaries

If you already followed my post about changing the dictionary to a UK English version you may be interested in this article in which the author has done what I wish I had found time for – a follow up on Graham’s work to find those other language files and perhaps a clue as to the engine being used here.

I’ll do a follow up post about the UK dictionary switch once I have Beta 3 installed.

Spread the word :

As several people have pointed out, Windows Live Writer (WLW) Beta comes with an American English dictionary by default. This is frustrating as it means I end up adding lots of things to my custom dictionary which I should not really need to do. I have also commented that it would be nice if it could look for and use (and share) my custom dictionary from MS Office. Why do I keep having to add my surname and street (for example) to a dictionary for every application? Isn’t it about time someone started using an Open format for dictionaries (maybe XML based like everything else these days)?

How to swap the US dictionary for a British one

In this blog post Graham Chastney describes how to swap the ssceam.clx file for sscebr2.clx. Interestingly my install has ssceam2 – perhaps a version number based on the fact I am running Beta2?

Anyway, his instructions are simply to swap the *AM*.clx file for a downloaded *BR*.clx file in Program Files\Windows Live Writer\Dictionaries by copying in and renaming, and essentially this works. The .clx file contains all kinds of clever dictionary things such as valid word endings, and this fixes all the -ised, -ising problems and so on. My recommendation is to rename the files by appending .us (rather than .old) so that it is more obvious which is which if you do want to swap between them.

However, what Graham neglects to mention is that the associated .tlx file is a list of 1000+ words including lots of the roots like color / colour so you really need to swap this too if you want to fix all of the spelling “mistakes”. If you leave this alone, then both “color” and “colour” will be accepted as correct spellings. This may suit you or you may prefer (as I do) to show US spellings as incorrect in which case you need to swap the .tlx file as well.

Swapping the files out without renaming causes WLW to fail at startup, and there seems to be no way to have more than one dictionary used “live” nor to choose a language in the GUI. Maybe there is some undocumented reg hack to set which one to use, but there is nothing obvious as the only value under the Live Writer key is to indicate the install path.

Why is Live Writer written like a bad third-party application?

EDIT: OK, this was simply wrong. After a couple of comments below I went back and checked. It was my mistake, I had been chasing something down and had my virtualised filestore open and switched windows while I was swapping dictionaries around. I screwed up. The user dictionary is in the roaming part of the profile, which is a really great place for it to live and exactly where I would want it to be kept. The whole of this paragraph is hereby stricken from the record. I apologise to readers for confusion and to the developers for the accusations.

Bad Adam – back in my box!

Incidentally, I find it really odd that WLW acts like a legacy application on Vista and stores the custom user dictionary in a virtualised folder …What happened to “eating your own dog food”? Bad dog, Microsoft – back in your box.

Spread the word :