Ten months later, and BlogJet 2.0 is starting to really suck

Last March, I had nothing but great things to say about BlogJet 2.0. It’s still a great blogging tool for the Windows platform–that is, if it were still March 2007. It’s January 2008 now, ten months later, and the fact that there hasn’t been any real bug fixes or improvements in all that time, really sucks.

Today, I finally narrowed down the simplest test case for a HTML generation bug in BlogJet that has been annoying me since I bought this software. I just posted a message about it in the “troubleshooting” forum, but in case you don’t check the forum, I’m repeating it here.

I’m using BlogJet 2.0.0.10 on WinXP Home SP2 and IE6. (No, I haven’t upgraded to IE7, yet.) Here are the steps to reproduce:

1. Start a new blog post.
2. In the post body, type:
   

   This is “a simple test.”

3. Select the words “a simple test” (not including the double quotes).
4. Press Ctrl-K to turn the selection into a hyperlink. Enter the following URL in the “Address” field. Click “OK”.
   

   http://test/?foo=bar&baz=bing

5. View the generated HTML source by pressing Ctrl-Tab.

What you get is:

This is "<A href="http://test/?foo="bar&amp;baz=bing"">a simple test</a>".

That is wrong. What it should have been is:

This is "<A href="http://test/?foo=bar&amp;baz=bing">a simple test</a>".

Where did the extra pair of double quotes come from? (e.g., around “bar&amp;baz=bing“)?

This might not seem like a big deal, but if you find yourself linking to phrases within double quotes and the link destination contains query parameters, this bug is going to bite you.

Please, someone, develop an open source replacement to BlogJet in 2008 and let me know about it. Hell, I’ll even help develop it …

Tags: BlogJet, bugs