Well ahead of the deadline posed by Google Translate API to stop working, we were finally able to compile this new release. This one followed a long period of problems that were presented by the older version, mainly because of the fact that Google decided to pose limitations on usage before their deadline which caused the previous versions support requests to surge to new heights. The Google change also triggered an API limit in the Bing translation API, since users were switching engines, which overloaded the Transposh hard coded API key for Bing.

nokuba, we survived this period to provide you with our latest and greatest version. This version fixes these problems be providing a bypass (Proxy for Google and temp keys for MSN) and it also allows you to use your own key directly (thanks to Randy fromspyware help centerfor providing us with his key for testing) which will take precedence over those other methods. While doing this we were able to dramatically improve the infrastructure of the plugin, changing the way AJAX calls were performed to a method that is native to WordPress (e.g. if your admin page works, it should probably work as well). While doing that we were able to reduce javascript code needed for the backend while allowing the translate all feature to work much faster (and supporting Apertium too!).

At this point we had a solid version, which seemed like a good thing to release, but no, we had to have some other features in, so we finally decided to tackle the issue of multiple widgets support (and title selection too, yippee!). Seems quite straight forward? but no, this caused a major rewrite of our widget infrastructure as well. Actually improving it quite drastically with changing the way css was added, and the way the widgets notified the servers of change in language (we now avoid a useless POST call to the server). While writing that we were lucky enough to stumble upon a PHP5.3 to PHP5.2 incompatibility issue with a set of other problems which held our release back another week. We want to thank the many users that have put up with our beta releases and helped us find problems that were hidden under layers of code and complexity.

We also took this opportunity to change our terms slightly, if you are displaying Google ads from AdSense on your translated pages, we will take 1/1000 of that space for use with our own adsense code, so if Transposh is helping you generate a revenue of $10K you will be buying us coffee! So thanks! To clarify things a bit, we don’t create additional ad space on your page, and we won’t insert any ads or change your layout, if you have no ads, we do nothing. If you think that this is asking too much, you may simply delete our plugin, whistle a soft tune, and be on your way. If you want a commercial license, we don’t sell them yet, but they’ll probably cost more.

Other changes to this version include:

Added Catalan and Hindi support for Bing – speaks for itself.

Dropdown widget improved css – it actually looks much better now.

Support for Memcached – if APC and other opcode caches were too much for you, now you may use memcached and have a lot of fun.

One day after summer has officially begun in the northern hemisphere, we are proud to present version 0.7.5 ye Java yethu. This version adds support for the new languages that were announced as supported today by Google Translate – Bengali, Gujarati, Kannada, Tamil and Telugu.

Before rushing to add those languages to your blog, please be reminded that those languages use an ajax proxy in order to work correctly, which means that they create a load on your server upon the first encounter with a new translation string (forcing it to fetch the translation from Google). So the choice is yours, but you have been notified…

Further more this version adds the option not to override the default locale with Transposh’s default language, this behavior (new on 0.7.4) allowed MU users to have admin pages in their language, but on the other hand annoyed users that wanted to manage the site in a language different than their default, so now this is configurable.

We have also improved the translation UI, the next and previous buttons now save changes done, and the dialog will not be re-centered upon clicking these buttons.

Yesterday we have released version 0.6.7. This version includes a few minor fixes, both for the ability to translate more phrases when google does not detect the source language correctly, and for the ability to include direct links to static files (those will cause a 301 redirect to occur).

However what is more important is that we have finally been able to cleanup our milestones, and set the gears in full motion for the next major version of Transposh – which will be 0.7. The focus of this version will be a major improvement to the translator frontend interface, and we have put the requirements for this online in our development site athttp://trac.transposh.org/wiki/milestones/0.7. Everyone that wants to influence the next version is welcomed to edit and comment on that wiki page or create a ticket for us. We will review each request and try to fit it into the schedule.

On some other news, we would like to thankColnect, our new sponsor for contributing a new vps for Transposh which will hopefully make the site go a bit faster. We have also attempted to use cloudflare to improve our service, however we are having mixed results with that, so if you are having any problems accessing this site, please let us know.

Last on the agenda, an alpha version of our plugin for blogger is on the works, if you have a site on blogger and want to add translation to it, just contact us.