Specifying Translation Options

Specifying Translation Options

After clicking Next in the Item Type page of the Bulk Translation wizard, the Options page opens. You use this page to specify translation options for the content items you selected in the previous page of the wizard.

The Options page of the wizard is displayed differently, depending on which Item Type you selected in the previous page of the wizard, because some translation options are relevant only for pages, and not for tags or I18N dictionaries.

  • Version displayed if Pages is selected in the Item Type page of the wizard.

  • Version displayed if Tags or I18N dictionaries is selected in the Item Type page of the wizard.

To specify translation options for the content items to send for translation:
  1. Enter the following information about the translation options:

Note: Your company’s configuration determines the default value of each option.

Option Description
Use Local TM This feature determines whether to check each component in the source version of the item for any content changes, and send only changed components out for translation. If a component was previously translated and it has not changed, then the Connector does not send it for translation again: Instead, it uses the stored translation. This feature reduces the quantity of content that the Connector sends to translation providers, which reduces your cost. However, it needs the Connector translation backup data, and it increases the Connector processing time before sending out the items for translation.

* If this check box is selected, the Connector checks whether content was already translated before sending it out for translation.
* If this check box is cleared, the Connector sends out content for translation without checking whether it has already been translated.

**Note about i18n dictionary items:** If this check box is selected, the Connector sends only previously untranslated i18n dictionary items for translation. If this check box is cleared, the Connector sends all i18n items for translation.
Select if using Blueprint/Live-copy This option is relevant when the target pages are MSM (Multi Site Manager) live copy pages, which means that Adobe Experience Manager automatically updates a target page when the corresponding source page changes. It prevents the Connector from overwriting unique source content that already exists in the target pages.

This is useful when you are sending a page for translation that has been used in the past to push content to other pages, and includes target page content which has been changed, for example, regionalized. In this scenario you do not want to overwrite the regionalized content as the translation process occurs. Select this option when you do not want the Connector to overwrite components in the target pages that include regionalized content with the newly translated content.

* If this check box is selected, the Connector does not overwrite unique source content that already exists in the target pages.
* If this check box is cleared, the Connector does overwrite unique source content that already exists in the target pages.

**Recommendation:** Select this check box if you are using the live-copy feature.

**Note:** This option is available only if **Pages** is selected in the **Item Type** page of the wizard.
Only translate content from locked components This option enables users to send out only content from locked components for translation.

* If this check box is selected, users can send out content for translation only if it is from a locked component.
* If this check box is cleared, users can send out content for translation whether or not it is from a locked component.

**Note:** Locked components have an inheritance relationship between a source Blueprint page and the connected live copy page. When sending content for translation using Sidekick, users can choose whether to send for translation the content from locked components, which is inherited from a Blueprint component. This is useful if, for example, the page has both global and regional information and you only want to translate (replace) the global content that is created via a Blueprint page. In this scenario, suppose that the regional content on the page is manually translated in house, and that it has not changed. You would not want to tamper with it. However, using the same scenario, the global content from head office has changed and needs translation. You would select this check box to separate the content and localize only the new, inherited content.

**Note about Blueprint pages:** If the Pickup Content From Blueprint Pages setting is specified, then the Connector always acts as though this option is selected, even if it is not selected. This occurs because only content from locked components are rolled out from Blueprint pages to Livecopy pages. For more information, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

**Note:** This option is available only if **Pages** is selected in the **Item Type** page of the wizard.
Unlock the component after translated content come back This option automatically unlocks a component after translated content returns.

This option is relevant only when the Select if using Blueprint/Live-copy is been selected. After translated content returns, it automatically unlocks a component, which breaks the MSM inheritance.

Warning: This breaks the inheritance between the component and its Blueprint page, so that it no longer inherits new content. However, you can use the CTCRestoreOriginalSync workflow to relock the component and recreate the inheritance. For details, see Relocking Unlocked Components.

* If this check box is selected, the Connector automatically unlocks a component after translated content returns.
* If this check box is cleared, the Connector does not automatically unlock a component after translated content returns.

**Note:** This option is available only if **Pages** is selected in the **Item Type** page of the wizard.
Allow translate content from Not-Sync’d components This option enables users to send content for translation even if it is not synchronized. This means it does not have a relationship to a Blueprint page, so it cannot be synchronized with it. This can happen if you are not using the MSM (Multi Site Manager) feature of Adobe Experience Manager, or if this is a page with regionalized content that does not inherit content from a Blueprint page.

* If this check box is selected, users can send out content for translation if it does not have a relationship to a Blueprint page.
* If this check box is cleared, users cannot send out content for translation if it does not have a relationship to a Blueprint page.

**Important:** The Connector treats certain page properties (jcr:content, jcr:title, jcr:description) as unlocked page properties. Therefore, if you want the Connector to send these page properties for translation, you must select this check box.

**Recommendation:** Select this check box if you are using either the live-copy or the language-copy features.

**Note about Blueprint pages:** If the Pickup Content From Blueprint Pages setting is specified, then the Connector always acts as though this option is selected, even when it is not. This occurs because only content from locked components is rolled out from Blueprint pages to Livecopy pages. For more information, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

**Note:** This option is available only if **Pages** is selected in the **Item Type** page of the wizard.
Translate page content Indicates whether to translate regular content fields in this content item.

Important: To send out words on pages for translation, you must select this check box.

Note: This option is available only if Pages is selected in the Item Type page of the wizard.
Translate Metadata Select this check box to send out for translation metadata fields that are defined in the Page Metadata Configuration section of the Advanced Settings page. These are properties under the /jcr:content node.

Note: This option is available only if Pages is selected in the Item Type page of the wizard.
Load existing translation to LocalTM first This option saves any target content that has already been translated to the local translation memory (TM) instead of sending it out for translation:

* When this option is selected:
* The Connector does not send out for translation entries that already have translations. Instead, it stores these translations in the local TM.
* The Connector sends out for translation only entries that do not have corresponding translations.
* When this option is not selected, the Connector overwrites any existing translated content.

**Tip:** Select the **Use Local TM** check box, described above, to instruct the Connector to check whether content was already translated before sending it out for translation.

**Note:** This option is available only if **Tags** or **i18n dictionaries** is selected in the **Item Type** page of the wizard.
Queue Metadata You can select the Level-2 Queue Metadata analysis code for these content items. If you add these items to the Translation Queue, you can filter and sort items there by this analysis code.

Note: Available only when using the Content API Translation Connector for Lionbridge Freeway. Displayed only when the Use Analysis Codes as Queue Metadata check box is selected in the Freeway Config section of the Configuration page. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.
  1. Do one of the following: