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

[vBET]

We already have solution how to support other translation services and how to handle it even when some service do not translate all to all languages.

At this moment we just finished coding it and we will start to test today/tomorrow. It will be tested only with Google now, but when it will be tested and working, then adding new services will be quite easy - just new class with 4 methods.

Actual solution still assumes that language detection if turned on will work only with Google, but if it will be necessary and other APIs will provide such possibility we will extend also this area.

We are still waiting for response from Microsoft about possibility to use their Translation API in vBET. As I wrote before we found no limitation in their Terms of Service, but we want to be sure. If there will be any limitation, then we will think about some workarounds. Like providing file with Microsoft Translation API usage for free - just upload to rest of vBET and it is working. Or something like that - we will see. First we need answer from Microsoft Translation API stuff

[vBET]

New code already tested and working. At this moment we are ready to add support for other translation services in quite easy way. We will keep you informed when we will have implemented alternative solution

[vBET]

I can officially confirm: we have solution to support alternative Translation API.

At this moment we have already working solution which uses Microsoft translation API (still some little issues with some special characters, but it will be solved).

When we close all little issues and test it well it will be included in next release

[vBET]

We have tested translations made by Microsoft on forum, blog, CMS, RSS channels, blog RSS channels and archive. It is working fine We also already have configurations added, so soon next release of vBET will support other translations APIs!

At this moment we have just few little things like - for how long we can cache Microsoft translations. How credits should be shown (logo, just text). And so on. So we are really close to next release

All our customers can sleep well we have alternative even when Google will be paid you will be able to use free APIs. Now only alternative is Microsoft, but we can easily add new APIs as it will be needed. We made more generic solution which allows us to add it easily

[vBET]

I just read whole TOS from Microsoft Translation API and found no limitation about caching results. Maybe I miss something. Does anybody found something about caching possibility for Microsoft Translation API?

[norku]

Great news guys. Well done

[vBET]

It is possible that we will make beta release today. Our code for supporting Microsoft translations is complete and tested. Now we are just checking one thing outside this area.

[Wulf]

What is the current status for the Microsoft translation integration? Agrees with the current version of Microsoft VBET possible translations to use?

[vBET]

At this moment vBET is already integrated with Microsoft Translation. At this very moment you can already use vBET with Microsoft Translation API under vBET4.x. It is not yet implemented for vBET 3.x version - so you cannot use it yet with vBulletin 3.x, but you can with vBulletin 4.x We will of course add also Microsoft Translation API support for vBET 3.x

[cesarica]

Paid version of Google Translate API now open for business - The official Google Code blog

Wednesday, August 24, 2011
Paid version of Google Translate API now open for business

By Jeff Chin, Product Manager

Back in May, we announced the deprecation of the free Translate API v1. Today, we’re introducing a paid version of the Google Translate API for businesses and commercial software developers. The Google Translate API provides a programmatic interface to access Google’s latest machine translation technology. This API supports translations between 50+ languages (more than 2500 language pairs) and is made possible by Google’s cloud infrastructure and large scale machine learning algorithms.

The paid version of Translate API removes many of the usage restrictions of previous versions and can now be used in commercial products. Translation costs $20 per million (M) characters of text translated (or approximately $0.05/page, assuming 500 words/page). You can sign up online via the APIs console for usage up to 50 M chars/month.

Developers who created projects in the API Console and started using the Translate API V2 prior to today will continue to receive a courtesy limit of 100K chars/day until December 1, 2011 or until they enable billing for their projects.

For academic users, we will continue to offer free access to the Google Translate Research API through our University Research Program for Google Translate. For website translations, we encourage you to use the Google Website Translator gadget which will continue to be free for use on all web sites. In addition, Google Translate, Translator Toolkit, the mobile translate apps for ****** and Android, and translation features within Chrome, Gmail, etc. will continue to be available to all users at no charge.

Jeff Chin is the Product Manager for Google Translate. Whenever he travels, Jeff enjoys learning and trying to speak the local language, and finding good local restaurants and food to eat.