Translations module settings

To access the Translations module setting in the backend, click Administration » Settings » Advanced » Translations.
You can configure the following:

You can choose which version of the content items, pages, or templates is send to the translators.

In SourceVersionType input field, enter one of the following:

• Draft
  

  The Translations module takes the last existing version of the content item and sends it for translation. This can be any kind of version – for example, a Draft version, an Awaiting approval version, or a Published version.

• Live
  The Translations module takes the last version that is Published. You may have other versions that are newer, but they will not be sent for translation. If the item does not have a Published version, the module takes the last version, regardless of its status.

If the translation agency requires mapping of neutral to specific language, you can set. For example, you may want to map English to US English or German to Austrian German.

In Cultures mapping input field, enter language to culture mappings, separated by semicolon.
For example, enter en -> en-us; de -> de-at

For each content type, you can choose which fields to translate. All fields that you do not explicitly exclude from translation are sent to the translation service. For example, you may not want to translate the name of the author of a news item or the URL of a page. 

To exclude fields from translation, perform the following:

1. Expand Translations » Strategies. 
2. Expand the content type whose translatable fields you want to configure and click PropertyMappings.
   All fields that are added to the mappings appear. 
3. To add a new field to the mappings, click Create new, enter the field name, and save your changes.
4. To make a field translatable, click the field and in Action, enter Translate.

   IMPORTANT: If you enable the translation of the UrlName field, the regular expression applied on the UrlName field once you import the translation is configurable from Advanced settings » System » Site URL Settings » URLRulesServer via the RegularExpressionFilter field.

5. To make a field non-translatable, click the field and in Action, enter DoNotTranslate.

NOTE: If you delete a mapping that is marked as DoNotTranslate by default, or a field is not added to the mappings, it will be translated. To make a property not translatable, you must explicitly add it to the mappings and mark it as DoNotTranslate.

You can set the interval at which the translation service checks for translations that are ready to be send to or received from the translation connector.

NOTE: Only the Send for translation now operations sends the items to the translations service immediately.

To do this, click Administration » Settings » Translations.

DISCLAIMER: This setting is available as of Sitefinity CMS version 13.3.7636.

In a multilingual site, when you create a page in one of the available languages and then send it for translation, the default localization strategy is set to Synced. To change the default localization strategy to Split, you need to configure the Parameters setting by performing the following:

1. Expand Translations » Strategies » Telerik.Sitefinity.Pages.Model.PageNode.
2. Under Property Mappings, click Parameters and then click Create new.
3. Create a new parameter in the following way:
   • In Key, enter localizationStrategy
   • In Value, enter Split
4. Click Save changes.

NOTE: After you stop the synchronization between the different languages, you will have different versions of that page. This means that you can edit each page translation separately.