The transposh.org wordpress plugin showcase and support site
by Ofer 2 Comments
A few days ago we silently released 0.5.4 which fixed a few bugs discovered in 0.5.3, mainly with the ajax and some edge cases with url translation. If the previous version works ok for you, there’s really no need to upgrade.
However – take the note, bugs opened on our trac (trac.transposh.org) are the ones that we are able to resolve fastest.
Enjoy this version and let us know what you think.
by Ofer 44 Comments
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.
by Ofer 32 Comments
This version emerged from a few requests by multilingual blogger (especially bi-linguals). This version allows suggesting the original language for a phrase (other than the default) using the html lang attribute.
The paragraph/phrase marked with a different language than the original would be left intact when the target language equals the language marked, but will be translated in other languages (even in the default language – when such support is enabled).
For example, the following phrase is written in Hebrew and surrounded with a span with lang=he attribute, if you’re reading it in another language, you will be able to read it in that other language (English included).
Hello you guys, in what language are you reading this paragraph?
It is now also possible to use the only_thislanguage class to mark a certain paragraph to appear only to readers in given language. A change in behaviour for this version is that now, the translate default version configuration option will only be used for non default marked paragraphs (and posts, see below regarding theme patches).
A patch would be provided to the default theme (didn’t decide if we’ll wait till version 3 of wordpress) that will enable marking a certain post’s original language, we’ll keep you posted.
Hope you enjoy this version.
by Ofer 2 Comments
This new version solves a very old problem with translating phrases longer than 255 characters. This change did not sacrifice speed, but actually enhanced it with a fine tuned index to match. By working on the database code we have also discovered a way to make the plugin perform much faster (mainly when APC caching was not used) where we now group many translation queries to the database into a single query.
A smaller bug with translation textarea tags was also solved thanks to timo.
Like always – looking forward for your feedbacks.
by Ofer 7 Comments
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.