Update to latest jquery-translate before 1 Dec 2011

They deprecated it but will not turn it off until the end of the year (December 31, 2011, as I understand it)

Since I use this on a site, never fear :-) It means I'll need to update it before the end of the year.

Nice to know somebody besides me is using this :-) I think it's a great addition to a site with users from many languages.

Looks like you're doing a very nice thing with the flags, which seem to be a non-module use of the module (using jquery-translate directly). I like it. Could you please post (probably in a new issue) a recipe of how you did this? It will help others.

Anyway, would love to have you do a little writeup on how to do this - a recipe for people. Your site looks quite nice.

This has to be done before they shut down the API on December 1, 2011

Thanks @zualas - I *will* be forced to get to this :-)

I took a look at this this morning, and there are a couple of problems.

1. It seems that the jquery translate plugin is now dependent on jQuery 1.5+, which means that I don't think there's any way it can work for Drupal 6 (jquery_update can only bring it up to 1.3).
2. With the Microsoft service, you must have a key, and the "free trial version" is good only for limited numbers of transactions. So the interface will change and we'll have to provide a way to configure the key.

The maintainer of the jquery.translate plugin is super responsive. He opened ticket 73 about this problem, so maybe there's hope.

The google/microsoft change is in ticket 70

If you're at all interested in this for Drupal 6, you might go vote for the Issue 73 to show your support for the maintainer. (Click the star at the bottom by the text "Vote for this issue and get email change notifications")

The maintainer indicates that the problem in #15 has been resolved, so perhaps we have a way forward here.

OK, so the maintainer fixed it all so that we can use D6 jquery and such...

But the Bing interface just flat doesn't work.

And the for-pay Google interface (v2; 1MB = $20.00) is not really working yet.

I pushed some experimental code to the 6.x-2.x branch, but it doesn't actually work, and IMO the jquery.translate code is not working yet.

I'm going to experiment with building a completely different module (much simpler) based on Google's Translate Tools, which may work.

For now, this is a "postponed", meaning that I expect this module to cease working on December 1.

I've subscribed to the jquery.translate issues, and if it seems to mature a bit I'll give it another shot.

There's no reason it can't be for D6 + D7 (if it works at all)

Overall, it looks to me like neither the MS solution nor the Google solution are actually free. MS has a come-on deal, but it looks pretty limited (and doesn't seem to work). Google's V2 will actually work I think once jquery.translate does the right things. It only costs $20 for a megabyte of translation. In my limited website, I think that would be fine. For others it might be terrible.

I did some research tonight on other Drupal modules and what they're doing:

http://drupal.org/project/i18n_auto - maintained by Greg.harvey, but uses deprecated google API. The issue in the issue queue does not have solutions.

http://drupal.org/project/gtranslate - actually a plug for a commercial module; seems to use Google Translation Tools instead of the API, doesn't work for me. Might work for some.

http://drupal.org/project/translate_this - Translate This button, which seems just like this module :-( But in http://drupal.org/node/1171992, he seems to hold out hope that something will work. It apparently uses http://translateth.is/ indirectly. However there's no indication on http://translateth.is that an update is being made.

http://drupal.org/project/gtranslate_links Google Translate links - Uses the actual translate web page, which might be relatively safe.

OK, I have just committed to both D6 and D7 versions that work with the for-pay Google API. Please test the dev version as soon as it's rolled and give me feedback. Google's pricing seems relatively fair to me at this point, but I don't yet know how much it will cost me in reality ($20/MB). You have to get a key and put your credit card information in. See http://code.google.com/apis/language/translate/v2/pricing.html for more information.

In addition to general code review and such

* Need an update.php that warns people that a key is now needed.
* Need a hook_requirements() that warns them about the key.

Or maybe the small audience will just figure this out.

No, I committed the changes to D6 as well. And tested. For Google Translate API v2, as described on the project page.

Ooops. I did accidentally push the 6.x work to a new 6.x-2.x branch. I've now committed it to the 6.x-1.x branch and created a new release.