MICROSOFT TRANSLATOR CODE

Switching from Google Translate API Version 2 to Microsoft Translator API is more direct. If not, then switching from Google Translate API Version 1 involves finding the function in your code, which calls, and replacing it with MicrosoftTranslateStart above, passing the text to be translated and the target language as arguments.

MICROSOFT TRANSLATOR CODE

If your code is set up in a similar way to the HTML and JavaScript above, then you can use the functions provided and just swap the function call in the form's onsubmit, and change the callback function to display the resulting translation wherever it is needed: google.load ('language', '1') function GoogleV1TranslateStart (text, language) Switching from Google to Microsoft The second function GoogleTranslateComplete is called by Google when the translation has been finished and pops up the result in a JavaScript alert. Then the function GoogleTranslateStart starts the translation, calling to translate from English (en) to Spanish (es). The first lines below load Google's JavaScript API library, and then Google's language library. Translate this: Īnd now the associated JavaScript code. The onsubmit returns false to prevent the form from actually submitting. When the Translate button is pressed, it calls the function GoogleTranslateStart, passing in the text to be translated and the language to translate to.

There is little point to actually implementing this as it will only be active for another month.įirst of all, create a basic HTML form used for all the examples below.

The code for version 1 is shown below, mainly so you can understand how it works. Even if you intend to pay Google for future translation services, you will still need to migrate away from this code, either to Google Translate API Version 2 or Microsoft Translator API. Version 1 was deprecated and will be shut off completely on 1 December 2011. Coding the Google Translate API Version 1

Microsoft translator