SharePoint Server 2013 introduces several new service applications; among them is the new Machine Translation Service. The new Machine Translation Service enables you to reach more people with new cloud-based translation services capable of translating not only sites, but also their content. These services have a comprehensive set of APIs, REST, and CSOM support, so content can be pre-translated when needed, or translated on the fly by users—asynchronously, synchronously, or streaming.
This article provides a Machine Translation Services overview including to references to other useful Machine Translation Services resources.
Machine Translation Services provides machine translation; machine translation is the use of software to translate text from one natural language such as English to another, such as German basically substituting one word in one natural language to its corresponding word in another (see illustration).
In Machine Translation Services the actual translation process is performed by a cloud-hosted machine translation service where processed requests are submitted.
There are a variety of methods that can be used to submit translation requests discussed further in this article.
Architecturally the Machine Translation Service shares several components with Word Automation Services introduced in SharePoint Server 2010 including Timer Jobs, Document Queues, etc. To that extent if you’re working with the server Object Model you’ll find similarities between Machine Translation Services and Word Automation Services including the Queue Manager/Schedule and Timer Job infrastructure which are responsible for the scheduling and adding of jobs to the Queue Database which also shares similarities with the Word Automation Services implementation in addition to the Application Manager which manages downloading files from content databases, creating and managing Application Workers, adding documents to Application Worker queues, and writing files back to a specified location.
The Application Worker Process; however, is unique to Machine Translation Services.
Machine Translation Services is capable of processing translation requests both synchronously and asynchronously. Jobs submitted to the Machine Translation Service synchronously are processed when the translation service timer job (SharePoint Translation Services) executes on its configurable, default interval of 15 minutes. Conversely jobs submitted synchronously are instantly translated as the synchronous working queue is prioritized over the asynchronous working queue.
Asynchronous requests can be also be processed manually by running the SharePoint Translation Services Timer Job Definition through SharePoint 2013 Central Administration or optionally through Windows PowerShell (see example below):
$job = Get-SPTimerJob “SharePoint Translation Services”
For Object Model and REST-based code samples related to the Machine Translation Service see also http://msdn.microsoft.com/en-us/library/jj163145(v=office.15).aspx.
Provisioning and Configuring the Machine Translation Service
To provision and configure the Machine Translation Service your environment must meet the following minimum requirements:
The App Management Service is started.
Server-to-server and app authentication is configured.
The User Profile Service Application Proxy must be in the Default Proxy Group and the User Profile Service provisioned and configured.
Internet connectivity is available.
Provision and Configure the Machine Translation Service
To learn more about provisioning and configuring Machine Translation Service see also http://technet.microsoft.com/en-us/library/jj553772(v=office.15).aspx.