Transposh - Breaking language barriers

The transposh.org wordpress plugin showcase and support site

Version 0.5.0 – Back up

by 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.

Version 0.4.2 – The answer?

by 14 Comments

What was the question? Anyone?
Maybe – Does this version support translation from Haitian? Yes
Maybe – Can Bing translate be used to generate auto translate? Yes
Maybe – Did you finish optimizations and reduced the script size to 1.5k when gzipped (with added functionality)? Yes

We hope you’ll enjoy this one as much as we do.

Version 0.4.1 – Faster for your clients

by 2 Comments

This new version includes the first part of optimizing the client side experience with transposh. Now, instead of loading libraries that might not be used, the plugin opts to load those upon demand. The first thing you can notice is that google translate api, microsoft translate api and jquery api are only loaded when they are really required. The script used by transposh has also been reduced in size and is now only 3kb of javascript. In the next step of optimization we will take out the edit interface part to a separate file.
Work was also done on optimizing the .css files, with a reduction in the number of inclusions so that under normal widget use there will only be one file used.
If anything breaks for you, on any browser or theme. Just let us know.
Unfortunately, this release won’t include support for jQuery 1.4 as there’s a bug in the jQuery UI tabs which prevents the upgrade at this point, We will probably upgrade once the next version of jQuery UI goes live.

Version 0.4.0 – Happy new integrations

by 25 Comments

This new version provides integrations with two of the most popular wordpress plugins. The first, google-xml-sitemaps provides a way to create sitemaps for use with google and google webmaster tools, the integration creates for each url in the sitemaps additional urls for the translated pages. This integration needs a simple patch to be performed on the original plugin, read how in the FAQ, or contact us to receive the patched file. We hope that future versions of google-xml-sitemaps will include this patch by default.

The second integration is with wp-super-cache which provides a caching mechanism for wordpress, this plugin is not for the faint of heart and provides a strong caching mechanism in exchange for tons of problems on the way, installation is hard and integration is even harder. However, this integration provides this plugin user a simple change which delete the cached page upon translation action, this prevents translations from happening multiple times and from users to see non-translated content (and in the case of auto-translation, translating again and again).

If you have more plugins you want integration with, and you have ideas on how (and maybe some code), just drop a note here. And yes – happy new decade to us all!

————

Update 2010/1/3 – It appears there was an error with the patch instructions, the new instructions are updated on this site FAQ section (thanks myatus). The patch can also be directly downloaded from this link : sitemap-core-322-patched