Hi,

As you may or may not be aware we have recently removed the Google Translate operation (although it will appear if you are already using it in a DataManager workflow). This is because from the 1st December Google translate will cease to be a free service, and Google will begin charging for it.

From tomorrow's 2.7 release we have added a new operation: "Translate text". This should be used in place of the old Google translate operation wherever possible. The translate text operation now uses the Microsoft BING translation service. This is free to use (at the moment). We have also created this operation so that we can add additional translation services in the future, for example we may add the Google translate paid service as an additional option.

The Microsoft BING translation service appears to work well, however we haven't had the opportunity to test it with large amounts of data or spend much time verifying the translation results. One useful piece of functionality that we have included is the ability to auto-detect the source language, meaning you can simply point the translate text operation at a text field without having to specify the language of the data. This would be particularly useful when you have data made up of several languages (for example the results of a twitter search).

Please let us know if you encounter any problems using the translate text operation. Also let us know if you know of any other translation services (free or paid) that we could include.

Chris