Google Translate API shut off or will be paid? Doesn't matter - vBET supports other APIs

[vBET]

Reports are available only for Google Translation API v2. For v1 are not and this API will be closed December 1st 2011, so there is no sense to do anything in this area.

At this moment language detection is supported only by Google Translation API (booth versions). We can add also support for Microsoft - we didn't do it yet, because we see some issues here. Microsoft Translation API supports less languages, so if you will have turned on more languages (those supported only by Google) then Microsoft translation API will be not able to detect the language. So in other words - we can add support for Microsoft Translation API language detection, but you can use it only when you use just languages supported for Microsoft. If you use one language more then Google must be used, otherwise detection will not work for languages not supported by Microsoft. This is the reason why we didn't add it from the beginning - it complicates configuration. Of course now we realize that many customers will stick only to free translations so we will add support for Microsoft Language Detection.

There is no rush here - as long as Google Translation API v1 is working you can still have free language detection. So first we will go for new vBET3.x release and add there support for other translation API. Then we will ass support for Microsoft Language Detection.

NOTE: at this moment in vBET4.x you can use Microsoft for translations and free Google Translation API v1 for detection. So you do not have to wait with switching. Language detection works separately - no matter what configuration you have for translation.

Also please note that Microsoft Translation API is much younger so it evolves a lot. Google translations wasn't so good as now from the beginning. Anyway - vBET gives you a choice to use free or paid translations. We also would be very happy, if Google wouldn't change their API to paid one... What is important now - adopt!