Posts Tagged trac
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 at http://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 thank Colnect, 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.
This new version allows urls on the site to be translated to given target languages. We would like to thank Hans from Cosmedia (a website about cosmetic surgery and treatments) for sponsoring the work done on this feature, as well as sponsoring a patch to support the custom permalinks plugin. If you are missing a feature, create a ticket for us at the development site and we’ll add it to our todo list. If you want to help us, sponsoring a feature development will help us make it happen faster, and the community to get a more complete product.
There are also further improvements included such as the fact that comments made at languages that are different than the default one are marked as such and become translatable at the default language (you need to mark the translate default language option in the settings), better support for wordpress super cache plugin, and a small upgrade in the jQueryUI version used that helps with wordpress 3.0 coming support.
Last item on this notice agenda is that we want you to know that we have a page on our development site where we maintain third party plugins compatibility list (with patches if required). On our wiki plugin support matrix page, as its a wiki, just create a user on the site and feel free to edit and improve this.
Today we have released v0.5.0 which is a relatively major change to the plugin as it offers two features that were requested by many.
The first one is the inclusion of a backup service inside the plugin. You can choose between either manually backing up, having the backup done for you daily or allowing the backup to happen live. Backup is only done for human translations, and in the live backup mode, the plugin simply sends the new translation to the backup service.
This backup service runs on top of the google appengine infrastructure, so its quite fast and scalable.
The second feature is the mass translate facility, now included in the transposh settings page. You can just hit the “Translate All Now” button and every page and post will be translated for you, slowly but surely. Note that the translation is done on the client side, and not the server side and with sufficient latency so there is no fear of your server abusing the automated translation service.
The next releases towards the 0.6.0 version will focus more on the user (translator) experience and multi-lingual blog wrtiting integrations.
Your ideas are always welcomed, just comment here or go to trac.transposh.org.