Up to 95% of the online content that companies generate is available in only one language. This is because localizing websites, especially beyond the home page, is cost prohibitive outside of the top few markets. As a result, localized content seldom extends one or two clicks beyond a home page.
However, with automatic translation from Microsoft Translator, content that wouldn’t otherwise be localized can be, and now most of your content can reach customers and partners worldwide.
With automatic translation you can make available, at little or no cost, all of your content in any Microsoft Translator supported language. Typical examples of this localized content include case studies, knowledge-base sites, technical-community forums, white papers, technical documentation, and help files.
Automatic translation provides a cost-effective means to test which localization option is optimal for you. For example, you may only have the budget to localize in one or two more languages or markets; by leveraging automatic translation you can cost-effectively localize in dozens of languages and measure customer response. Using your existing web analytics you will be able to decide where to invest in human translation in terms of markets, languages, or pages. In addition, you will still be able to maintain automatic translation for other areas, to maintain reach.
By combining pure automatic translation with community-driven improvement or paid translation resources, you can select different quality levels for your translations based on business criteria and needs.
Expand the sections below to learn more on how to use Translator for your Web Localization needs.Show all
The Widget is the easiest, fastest, and most cost-effective way to integrate page localization on your website. The Widget supports most website technologies.
For improved quality, customers can use the Translator Hub to build customized language models and the Collaborative Translation Framework (CTF) to enable community-sourced improvements of the automatically generated translations.
The limitation of the Widget technology is that a floating widget window will remain on translated pages, which is suboptimal in some situations. You can see the Widget at work on the Windows Team Blog.
Customers can also use third-party localization partners to review and correct pre-translated text through CTF. Partners
offering support for these good/better/best approaches can be found in the
Learn more about the Widget.
The next level in integrating automatic translation is to use the Translator API to publish websites in local languages (versus having just one site that is translated through the Widget). For example, customers using Adobe Experience Manager (AEM) can now natively support this model by simply entering their client ID in Adobe’s product. Learn more about AEM support for Microsoft Translator.
Learn more about Microsoft Translator API.