Kentico CMS 7: Translation services

Version 7 greatly enhances the process of creating multilingual websites by introducing the support of various types of translation services. I’d like to provide you with a brief description of this brand new module which makes it easier to automate the process of creating multilingual web solutions.
Translation service providers

To automate the translation process as much as possible there is a general model of translation service providers of two types.

One type involves machine translators such as Microsoft Bing Translator or Google Translator. Making editors work much easier, these translator services can now be queried directly from within the CMS UI. You simply click the icon of the desired service and your text is translated by that service.

Second type uses classic translation services. Version 7 includes ready-prepared full integration with the worldwide translation service as well as other providers, which allow automatic translation submission via e-mail and/or file system.

There is of course the possibility of writing your own custom service provider (with similar support to e-commerce payment gateways).

Translation of the documents

You will see a new option in the content tree to create a new culture version, as depicted below:

Translation submission is also supported as a bulk operation, so you can conveniently submit all the documents you need translated.

Once you submit the document(s) for translation, the target culture version is created as a copy of source culture version indicating that the document is awaiting translation (blue circle in the content tree).

You can manage your translation submissions in the CMS Desk / Tools / Translations section. You can see the status of the submission, browse through the translated documents and import approved translations.

REST translation service

Since the whole translation process is based on a universal xml-based format XLIFF, which is supported by all main translation services and SW for translators, it couldn’t be easier to provide a general interface for any translation service to integrate with Kentico CMS.

This is done by providing translation REST service. It will be possible to receive and submit any document in XLIFF format via the REST service.

I hope your content editors will like this module and that it will enable them to work more comfortably and efficiently in the multilingual website setting.

Please feel free to submit your opinions and suggestions using the comment section below!

Update - Licensing

The new features for Translation Management and integration with translation services will be only available in Kentico EMS.
Share this article on   LinkedIn


Petr Palas commented on

@rvo: I believe this feature will bring most value to organizations with complex translation needs which are typically mid-to-large international companies and that's the market segment for Kentico EMS.

rvo commented on

Very disappointing that this feature is only included in Kentico EMS. Would it be possible to include it in Kentico CMS Ultimate?After all, the feature is more closely related to content than enterprise marketing.

stepank-kentico commented on

Other providers provided out-of-the-box are rather generic providers (not an integration with a specific translation service).

Example is an e-mail provider which allows automatic submission via e-mail or a provider which exports submissions as a zip file to specified export folder and automatically imports translations from specified import folder.

andy commented on

great! what are the other out of the box classic type translation services you are looking at alongside, understanding that the list might change.

Andy commented on

Good post
- you say " as well as other providers,"

obviously this is still in progress, but do you have a list of candidate "other providers".

I recognize that the REST API will allow fairly easy custom integration, but very interested in who else might be included out of the box.

Neil Powers commented on

Great post!!! This feature is asked for several times in sales demos, technical demos and more. I can't wait for 7.0

stepank-kentico commented on

Hi Sergey,

thanks for your comment! The circles are displayed on the right side on purpose - because of design. There can be more of them displayed at once and than the tree would look inconsistent.

You don't need to resize the whole tree, for long names you can scroll the tree while preserving size.

Sergey commented on

Very nice, it will be helpful for sure!

>>Once you submit the document(s) for translation, the target culture version is created as a copy of source culture version indicating that the document is awaiting translation (blue circle in the content tree).

You will not be able to see blue circle in case you have node with long title, to see it you will have to resize tree. Maybe it is better to move circles to the left?

Jeroen Fürst commented on

Great first post Stepan! Hmmm I wonder where I have seen a similar translation integration before ;)