WordPress 2.4 has been cancelled, and we’ll be going straight to 2.5 in early March. Tarski 2.1 is being written for compatibility with that next version, and hence will be delayed until then too. Keep track of our plans for the release on the roadmap page (which has just moved from the ‘Help’ section to the ‘About’ section).

The major feature of Tarski 2.1 thus far is the move to entirely widgetised footers and sidebars. I’m in the midst of writing and testing an upgrade script to convert people’s current options to the new widget-based ones. If you have any comments or suggestions about that, please post on the forum. Patches, bug reports etc. should be posted on the issue tracker ticket for the changes.

I’ve updated the website with a link to the Tarski Subversion repository, specifically to the latest stable branch (which is what you should be using; 2.0.5 is the latest release from that branch). Hopefully more people will try using svn to keep their WordPress and Tarski installations updated; it’s a little more work initially, but it makes maintenance far, far easier, as well as allowing you to take advantage of the latest security fixes, general bug fixes, and other improvements with the minimum of effort. There are a bunch of tutorials out there on this subject (for example, this one). If people are interested I can write up a quick tutorial on how I keep things up to date on this site.

The changelog is briefer than usual, but I like to think this is a good thing: there were fewer things to fix. A couple of them could have been classified as ‘tweaks’, specifically the Internet Explorer issues, but since they broke the proper display of some elements in that browser it seemed more accurate to call them bugs.

If we receive more translations before the next major version comes out, we’d be happy to release another iteration of the 1.2.x branch. All the details, as ever, are on the localisation page. It’s great that Tarski is now available in five languages (other than English), but we’d very much like to add to that. Various feature additions and amendments are planned to improve matters still further on this front, but if you have any suggestions don’t hesitate to post them on the forum.

Thanks again to everyone who’s helped us out with Tarski, particularly those who’ve contributed translations and brought bugs to our attention, and I hope you enjoy using Tarski 1.2.3.

Bugs and suggestions should be posted on the forum.

An updated POT is now up. I know this has been frustrating our translators so it’s cheering to finally have a fix. If there are any other bits of text that aren’t yet localisable, please let us know in the forum or in the comments on this post.

In addition to this, we’re still looking for more translations for 1.2.3, so if you’re able to translate Tarski into another language (that hasn’t already been covered by someone else) please get in touch.

Chris and I hope to get back to working on 1.2 shortly—the frontend code is all there, we just need to finish up the new options page, tie it into the new loop code, and test it. We’ll keep you abrest of our progress.

We’re still dealing with support queries on the forum, so if you have a Tarski mod or custom style you’d like to show off, or just need some help sorting something out, drop by and give us a shout.

Firstly, I’ve rewritten a fair amount of the CSS, to make it more flexible and extensible. Content areas (such as entries, comments and so on) are now denoted by the content class, while the two columns are referred to by primary and secondary classes. This replaces a large and disparate set of classes and ids, making the code cleaner and easier to extend and modify. Additional stylesheets, for example, should now be much easier to write.

Secondly, Chris has been working on the Tarski Options page, cleaning it up and improving it substantially. We hope that the new version will be easier and more intuitive to use.

There are also the usual raft of tweaks and improvements, including the much-requested pagination and next/previous links, better trackback and language support, and a new and improved loop.php file which should make modifications based on the Tarski code much easier to implement.

1.2 beta test

Because there are such substantial alterations to the code, we want to run a small test before releasing it publicly. Sign up for the 1.2 beta on this forum thread.

Beta applications are now closed.

The roadmap gives a fairly good idea of what else will be included in the new release when it comes out, later this week.