Version 0.9.0 – Ready, settings, go!

On the 12/12/12 (what a lovely date) at 20:12 (an appropriate time). We have released version 0.9.0 of our plugin. This version included a major rewrite of our settings and administration page. Moving from the single very long page with oh so many options to a slick tabbed interface.
This version is not only cosmetic but it also included two major features enabled by the settings new advanced tab:
1. Inclusion of debugging support: Now we will be able to give you better support using the plugin ability to create logs, and allow remote debugging.
2. Advanced parsing rules: This feature allows you to change the way texts are being broken for translation on your site. It allows a much finer granulation and fitting the engine to your specific use case.

However – be warned, those features, although well tested are marked advanced and experimental. Use them only if you understand what you are doing.

There are so many other features and bug fixes included, that many of them deserve their own post, but for now, lets go over the change log:
* A new language selection widget based on select2 (Very nice select box with flags)
* Added ctrl keys for quick navigation of previous/next blocks (Improves speed of working with the interface)
* A new option that allows to reset the configuration file to the recommanded defaults
* Css fixes for twenty twelve theme
* Avoid loading the subwidgets in the admin pages
* Removed distinction between editable and viewable languages, now a language can only be active or disabled
* Updating jQueriUI to 1.9.2 (jQuery should now be 1.6+)
* Fixes the z-index for the old style dropdown (patch by chemaz)
* Fixes the bug with the coupling of Chinese simple and traditional
* Fix bug preventing upgrade from very old versions
* Suppress notices when widgets are created directly with our function
* Avoid rewriting urls in the default language, mainly effected canonicals
* Our script is needed when the widget allows setting of default language
* Finally solved the problem with MSN translate and CR/LF

In the days following the initial release, three bugs have been uncovered and fixed, if something simple is not working, make sure to refresh your files.

Enjoy this version!

Version 0.8.5 – We support Lao too

A frog and a mouse welcome Laos

Well, Google just announced on their translate blog that they will support Lao, the official language of Laos, so we have added the code required and did a quick release with support to this language, which is also supported by One Hour Translation.

The version is already out for a few days but the real problem with getting this post live was finding a picture. We are not quite sure it is the most appropriate picture, but at least it rhymes.

Enjoy this new version.

Version 0.8.4 – Professional human translation is here

Professional work
Professional work
Less professional work
Less professional work

We are very proud to present this release of our plugin.

This version, in addition to normal enhancements and bug fixes, finally integrates professional human translation with a basic integration with OneHourTranslation.com professional translation service.


The way this works is the following:

  • Go to OneHourTranslaion.com and create an account
  • Use the account details generated and insert them to Transposh’s settings page
  • When using the translation interface, an admin (and only an admin) will see a “One Hour Translation queue” button
  • Pressing this button will add the phrase to a queue, another click will dequeue the item
  • 10 minutes after the last phrase was added a translation project will be generated on one hour translation
  • Give it an hour (or less from our experience) and the translations will appear on your site
  • Everybody is happy and you actually support the Transposh project (Yay!)

This is rather new, so if Murphy strikes, just contact us and we’ll do whatever we can to make things work.

Now, for the rest of this release:

  • Fixed flag of Swahili to Tanzania as noted by Ed Jordan
  • Lots of fixes to backup service
  • Fix for a parser bug when having translate in default language following a select element
  • Fixed XSS reported by Infern0_ (big thanks!)
  • For programmers: Added a global function to return the current language “transposh_get_current_language()
  • Seems like Lybia has a new flag too 😉
  • Fixed widget IDs containing a backslash so that we’ll pass w3c validation
  • Updated jQueryUI to 1.8.23 to avoid conflict with jQuery 1.8 used by some themes
  • Portuguese (Brazil) translation by Amilton Junior

Our operators are waiting for your feedback, if you get a busy signal, try contacting us again!

P.S. This is the very first version to have passed 1,000 daily downloads, we are humbled.

Version 0.8.2 – 3 years, 66 languages, 1 wordpress

I said 3 candles on that cake!

It has been three years (and three days, and thirty three hours) since the first version of Transposh plugin has been aired on the wordpress.org plugin repository.

Time surely flies.

This has been the first leap year (29th February) and a real leap year for Transposh. The plugin has been downloaded from the repository over 50,000 times this year and has made a steady growth of features and total number of languages supported. And today with the addition of Hmong Daw we are the first plugin to support a total number of 66 languages.

This was a really interesting (as in, have an interesting life) year for the automatic translation industry and plugins, where Google has nearly dropped their API support (only to switch to a pay model) while Bing imposed new limits. Transposh has successfully overcame those changes, while other plugins did not survive.

What does the future holds for Transposh? We are slowly boiling some new stuff, working on our vision to improve website translation, when things will be ready – they will be out. Meanwhile, your continued support is important to us, sometimes a simple email with “your plugin is great” drives us to continue. So if you believe we are doing well, drop us a line, if you think we should improve things, drop us a note, and if you think that we suck, we fail to understand why you have read this message up to this point 😉

Wishing ourselves a great 4th year, maybe it will end with a bigger cake :)