As the world becomes smaller through the use of many modern communication methods, language differences still create a wall between people of different cultures. How can this barrier be overcome when creating software or websites? The answer lies in machine translation. This documentation will help developers get started using the Microsoft Translator API in software or web sites using any of fice interfaces: a Web widget, AJAX, HTTP, SOAP, or oData.
As a developer or site owner you feel the responsibility to ensure that your website, service or application has a global reach. Making it available on the World Wide Web is one thing, but ensuring that your service (or message) is truly accessible to people all over the world is quite another challenge. Opting for machine translation might be the most effective way of reaching the world's connected population, but the best machine translation technology cannot always provide translations tailored to a site or users like a human translator would. Further, many websites are selective about the content they have translated by human translators due to not just the initial cost of translation, but also the need to continually invest whenever the site is updated. Similarly, it is impossible for apps that deliver content to their users to expect to use professional human translators for translation. Enter Microsoft Translator.
Microsoft Translator will do the heavy lifting for you. For site owners, the Microsoft Translator widget or AJAX API seamlessly integrates with the site to translate the content and reflect any changes as they happen with no extra effort. In addition to keeping your users on your site, Microsoft Translator widget now also offers the unique ability to improve the grammatical and contextual accuracy of the delivered translations. This is done through the new AddTranslation() and GetTranslations() methods, which are, together with the full integration into all Translate() methods is called the Collaborative Translatiosn Framework . This functionality is also available for further customization and consumption through SOAP, HTTP and AJAX interfaces.