Settings - Translation services

Enable translation services

Enabling this setting allows users to create new language versions of pages and localize text values via translation services. The available translation options are determined by the other settings in this category.

Allow attachment translation

Determines whether the system submits page file attachments (without their image variants) for translation along with the main content of pages.

Translation attachments file types

May be used to limit which attachment file types can be submitted for translation. Entered as a list of allowed file extensions separated by semicolons, for example: txt;docx;pdf

If empty, all types of attached files are included in page translations.

Translate web part properties

Determines if text values entered into the properties of web parts are also submitted for translation. This allows translation of content added onto pages via text web parts such as Static text.

Only properties that have the Translate field flag enabled in the web part definition are included. By default, this setting is disabled for the majority of web part properties. You can configure this for specific web parts in the Web parts application by editing their properties on the Properties tab.

When the translation is imported, the system creates a resource string for each property, containing the translated values in the given languages. The original text values of the properties are replaced by localization macros, which insert the appropriate resource strings.

Automatically import translated submissions

If enabled, the system automatically inserts translated content into pages when the data is imported into submissions.

Warning: This overwrites pages immediately when a service finishes the translations, without the approval of administrators.

With this setting disabled, users need to manually process completed translation submissions in the Translations application.

Encoding to use

Sets the character encoding type for the XLIFF pages used to transfer translation data in and out of the system. For example: utf-8

Enable REST translation service

Enables or disables the translation REST service, which may be used to retrieve the data of pages and other types of objects in XLIFF format. It is also possible to import translated XLIFF data via REST.

The translation REST service is not affected by the general REST settings, which can be configured in Settings -> Integration -> REST.

Translation submission export folder

Specifies the path of the folder in the file system where the service creates the zip packages with the translation source data (XLIFF files and instructions) when pages are submitted for manual translation.

If empty, the ~/App_Data/Translations/Export/ folder is used.

Translations import folder

Sets the path of the folder from which the system imports zip packages containing completed translations.

If empty, the ~/App_Data/Translations/Import/ folder is used.

Delete ZIP after successful download

If enabled, the system deletes the zip packages containing finished translations after importing the XLIFF data (the submissions can be managed in the Translations application).

Translation submission recipients

Specifies the addresses to which the system sends translation assignments when submissions are created for the email service. You can enter multiple email addresses, separated by semicolons.

To assign different translator addresses for specific languages:

1. Open the Translation services application.
2. Create a Clone of the Translation via e-mail service for each additional language.
3. Edit the services and enter the appropriate translator addresses into the Translation submission recipients property. This property overrides the Default email sender setting.

Default email sender

When sending translation assignment emails, the system automatically sets the sender to the address of the user who submitted the translation. The value of this setting is used if no user address is available, for example in the case of translations submitted automatically or via the API.

API Key

Note: The functionality for submitting content for translation to Microsoft Translator no longer works in this version of Kentico. If you wish to use this functionality, you need to upgrade to Kentico 12 or newer.

API Key

Enter a valid API Key, used by the Google Translator service to identify the application’s translation project. You can obtain the key from the Google APIs console.

Project Director URL

The URL of your project that you received when setting up the service at Translations.com.

Client user name

Sets the user name under which the application accesses the Translations.com service.

Client user password

Enter the password matching the client user name.

Project short code

A code string used to identify your translation project.