Probably the major abuses have prompted Google to stop developing Translate API and switch it off. However, the translations will still be able to benefit those who pay for them.
End of Google Translate API v1 established on 1 December this year. This probably means that the end of the year to stop working joomla modules for automatic translation. Google has decided that in May 2011, after a wave of APIs and service abuse. Spammers routinely used the Translate API for distributed automatic translation of texts, while the owners of “farm content” and online forums possessed automatically translated content to get better placement in search results.
Commercial Translate API v2 will not have many restrictions imposed on the previous version of the interface and could be used by commercial products (like Ortsbo) for a fee. The courtesy limit for existing Translate API v2 projects created prior to August 24, 2011 will be reduced to zero on Dec 1, 2011. The new API will ensure access to supports over 50 languages, machine translation system that runs on Google’s cloud. Service is to be paid from the mark. Million characters will cost $20, which gives a price of about 5 cents per page (if we assume that the site contains 500 words). You can now buy up to 50 million characters per month through Google APIs console.
While business and commercial web developers will now have to pay, academic users will still have free access to the Google Translate Research API. Fortunately, also provided free of charge remain applications for Android and IOS, Translator Toolkit, Google Translate page and translations in Chrome, Gmail and other Google products.
Does web delevopers turn to the services offered by the Microsoft Translator AJAX API?