Although I’ve shut down new subscriptions to the SharePoint 2013 Beta series (pending a new series titled “Introducing SharePoint 2013” that starts as soon as the public beta of SharePoint 2013 comes out) I still have a blog that needs a bit of TLC.
Here’s an excerpt from issue 5 of SharePoint 2013 Beta, regarding a new feature.
In the very first issue of this series, I briefly mentioned a new feature of SharePoint called translation services. I again briefly mentioned this in the previous issue, and I thought I should expand a bit on that service because I think it’s a potential great feature.
SharePoint 2013 will support automatic machine translations of documents. This will allow users to send documents for translation and get a new language version of that document returned.
Consider for example that you have a multi-national organization that primarily uses English, Spanish, and German to produce documents, or a government agency required to have documents available in both English and Spanish.
Now, rather than having to rely on slow and potentially expensive manual translations of documents, SharePoint users can instead submit documents for translation jobs that will turn the document both to and from other languages than their original language.
If you’ve ever worked with machine translations such as Google Translate or Bing Translate, however, you’ll probably know that these translations are far from perfect.
I’m quite certain that Microsoft has not come up with a perfect solution, but sometimes convenience is more important than perfect accuracy. Most uses I’ve seen of machine translation are not to produce perfectly new documents but rather to get a general understanding of what a piece of text means.
Further, even a rough machine translation will be a good starting point for a later manual translation refinement.
Machine translations happen on the SharePoint server, but users can initiate translations from any client, including client-side object model clients such as mobile or external web pages.
Translation happens by creating a translation item, which contains the path to both the source and destination documents. Users can also submit entire libraries or folders for translation, in which case all translatable documents in that folder will be submitted for translation.
Note: Only certain file types are translatable, and although it’s not clear which types will be supported, it’s safe to assume that at least Word and possibly PowerPoint will be on the list. Less likely are non-Office types, including PDF documents.
However, certain properties of the protocol documentation indicate that the file types available for translation is extensible, so it may be that third-party vendors can add new file types to proprietary file types.
A translation item can also specify what happens in the case of an existing item. For example, if your translate item destination is DocumentGerman.docx, and that file already exist, you can choose to add a new item to that document’s version history rather than overwrite the existing file.
After creating a translation item, the user then submits the item to a translation job, which is a queued item that will be responsible for the actual translation. The translation job is submitted to the server for processing, to be performed when the server has capacity to do so.
A translation job also contains the language for the destination job. As such, it seems that if you want to translate a single document into several different languages, you actually need to submit the document several times. Conversely, if you have a number of documents that you want to translate into a single new language, you can submit all those documents as a single translation job.
There’s also the concept of an immediate translation job that is essentially a single document to be translated with a higher priority than other jobs.
It is not clear what types of languages SharePoint machine translations support. However, it is at least likely that it will be possible to extend the available languages for the same reasons it seems likely that you can extend the supported file types. This may be through language packs, perhaps even as freely available language packs downloadable like any regular interface language packs from Microsoft.
It is also likely that users of Office 2013 will be able to translate documents directly from client applications. Word already supports Bing translations directly from the application, and through Agaves, a new extensibility feature of Office that allows plugins to Office, users should be able to connect to SharePoint machine translations as well.
Note: Keep in mind that this will be a version 1.0 for Microsoft. From experience, it is likely that this will mean a fair number of baby teeth problems likely resulting in a lot of crying and sleepless nights for those responsible.
As mentioned, I’ve stopped accepting new subscriptions for the SharePoint 2013 Beta series. If you’d like to be kept up-to-date on the new series titled “Introducing SharePoint 2013”, feel free to drop by the site to sign up for the USP Journal mailing list.
Found this article valuable? Want to show your appreciation? Here are some options:
a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.
b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.
c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!