Posts Tagged wordpress plugin

Version 0.5.7 – Pluggable widgets

Octopus by Dr. Dwayne Meadows, NOAA/NMFS/OPR

Paul is being interviewed by Transposh team

We invited Paul the octopus to Transposh for a couple of beers following his latest success in the world cup. We asked him to make a few predictions for us regarding the coming version of Transposh, and since after drinking too much he was really cooperative we had the chance to make an exclusive interview with him.

We first asked him about the new version of Transposh, the one with support for writing your own language widget (want to know how? go to our widget writing guide). He said that as an octopus he really likes things with sockets or things that are pluggable anyhow, so he predicted this feature will be a great success (after seeing the javascript based widget sample). He also gave us a fair warning that if someone misses those ul tags (and know what they meant) they can quickly code their own widget.

After that part he became kinda silent, and reminded us by winking that octopuses can’t really talk. So we decided to go for the two boxes trickery, we put a box with a nice picture of a big, and another one with a picture of a feature (huh?), and we waited for him to open whichever box he saw fit. Naturally he opened the bug box, which we saw as a reason to write the normal warning that bugs might even slip through our testing (even with the help of an eight armed prophet working for us on QA). We also used the opportunity to write a quick guide on how to get a development version for debugging on our wiki.

And last note, whoever wants to give us a hand (or leg), or wants to share his widget creation with the world is more than welcomed to contact us.

Enjoy today’s match, any questions to Paul will be forwarded directly to him.

P.S – usual share of bug fixes are in, fixed a few languages in msn translate and added a few languages to the settings (still not auto translatable – but will soon be)

Update: thanks to a critical bug found in some situations, 0.5.6 was promptly replaced with 0.5.7 thanks for all those who reported this, with special thanks to dgrut.

, , , , ,

37 Comments

Version 0.5.5 – Buddypress Support

Did you arm your vuvuzelas yet for the wordpress 3.0 release? Now you can do that and enjoy the fact that the latest transposh plugin for wordpress offers support for the new wordpress, and as a bonus, support for buddypress. This support for buddypress now means that urls generated and answered by it will now be translatable.

More changes include additional support for conditions that made the UI unworkable, when for example jQuery tools was used with some plugin or theme, now – we are able to make it work.

Like previously since a new major version of wordpress is out, we are dropping official support for the older wordpress 2.8 version, the plugin should still function but it will not be tested and patched for that version and we recommend that you upgrade.

As always – we want to hear you out, what features you want? and which team will win the world cup?  just drop your comments here.

, , , ,

20 Comments

Version 0.5.2 – Improved lang attribute support

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

, ,

32 Comments

Version 0.5.1 – Database improvements

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.

, , ,

2 Comments

Version 0.5.0 – Back up

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.

, , , ,

7 Comments

Version 0.4.3 – Our wordpress plugin anniversary

One year birthdayOne year and 13,000 downloads later, we are happy to release version 0.4.3.
This version brings in more compatibility with some themes and better parsing of $ and % symbols.

Anyone wants to guess the number of downloads we will have next year?

, , ,

2 Comments

Version 0.4.2 – The answer?

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.

, , , , ,

14 Comments

Version 0.4.1 – Faster for your clients

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.

, , ,

2 Comments

Version 0.4.0 – Happy new integrations

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

, , , ,

25 Comments

Version 0.3.9 – More flexibility

The new version includes two major features. The first is the ability to sort the languages on the widget, you can now put your default language first or move languages around in any way you like. Icons have appeared that tell you if the language is supported by bing and google and if the language is written form right to left. You can also switch between the original name of the language and its English name, so understanding which language is which becomes even cleared.

We have also moved some files around and enabled an ajax entry file, this makes the alternate post settings redundant (we hope, let us know if you find bugs) and makes things generally snappier. If you are used to just unzipping the new version over the old one, it is now safe to delete all files that are not in sub-directories (save for transposh.php) heck, we even recommend that…

Some more exciting features are planned for the next release, and if you want to keep informed. Follow our twitter stream…

, , , ,

5 Comments