|Translation on Sidekick||
This setting determines the user interface displayed when clicking Translate Content on the Page tab of the Sidekick. Some companies prefer a simplified process where users cannot choose advanced translation options, while others prefer to empower their content editors to set various parameters each time they send out content. For instance contributors can choose to ensure source content is not overwritten during the translation process, as it pertains to MSM rollout processes. The following options are available:
For more information about these options, including screen captures of the user interfaces displayed in Sidekick, see Sidekick Options.
|Show options on Bulk UI||
This setting determines whether to display the Options page in the Bulk Translation wizard. The Options page enables users to change the following options:
These options are individually configurable, and they are described in the Translation Default Settings section, below.
|Show options on Touch UI||
This setting determines whether to display the Options tab in the Translate Content page, which opens from Adobe Experience Manager's Touch-Optimized UI. The Options tab enables users to change the following options:
These options are individually configurable, and they are described in the Translation Default Settings section, below.
Note: This is displayed only in Adobe Experience Manager versions 6.3 and higher, and it is relevant only for those versions.
|Indicate SEO field in translation file||
You can include SEO flags in XML translation files to indicate page field and property translations that must be Search Engine Optimized (SEO). Select the method for including this information in the file:
SEO_Flag="This is a SEO field" <=== this text "This is a SEO field" is configurated in Metadata config
The next field is a SEO field <=== this text "The next field is a SEO field" is configurated in Metadata config
If you select No (the default value), then the Connector does not include SEO flags in the XML translation files.
Important: If you specify this setting, you must specify which SEO flags to include in the Page Metadata Configuration section of the Advanced Settings page. For details, see Configuring which Page Metadata is Available for Copying and Translation.
|Allow Reference Files for Translation Job||Select this check box to enable users to attach references files (support assets) when sending out a translation job. This determines whether the Reference Files feature is available in the Translation Queue, Bulk Translation Wizard, Globalization Tool, and the Sidekick wizard.|
|Translate Asset Metadata||
Select this check box to enable users to send out properties of digital-asset metadata properties for translation. For more information about this feature, see Configuring Translation Settings for Digital Assets.
Important: You must configure the asset properties to send for translation in the Component Mapping page, in the same way that you configure other component. After you click Collect for an asset to add it to the component list, you must click Set for all components to send all components with a specific property for translation. For detailed instructions, see Configuring which Components and Properties to Send Out for Translation
|Translate Asset Binary||
Select this check box to enable users to send out digital assets for translation, for example, actual JPG or PDF files. For more information about this feature, see Configuring Translation Settings for Digital Assets.
Tip: In the Exceptions text field, you can prevent assets with specific file-type extensions or asset paths from being sent out for translation. Separate each file type or path with a comma ( , ), for example: gif,jpg,png,perform.ppt,/products/docs/guide.pdf You can use the exclamation mark ( ! ) wild-card character as a prefix for file names to exclude, for example: !NeedTrans.pdf.
Note: When the Connector sends the actual asset for translation, it sends the original rendition. There may be multiple renditions of an asset, for example, there may be multiple versions of an image with different resolutions, such as for Web and print. For more information, refer to "Managing Renditions" in the Adobe Experience Manager documentation, at: https://docs.adobe.com/docs/en/aem/6-3/author/assets/managing-assets-touch-ui.html#Managing%20Renditions.
|Show Globalization Tool||Select this check box to display the Globalization Tool menu item in the Lionbridge Connector rail and the corresponding Globalization Tool. You can use the Globalization Tool to perform actions on multiple pages simultaneously. For a detailed description of this feature, refer to the Lionbridge Connector for Adobe Experience Manager User Guide.|
|Use user session in page search||
This setting determines whether the Connector uses Adobe Experience Manager's built-in permission settings so that a user can access only part of the content repository.
Tip: You can also limit a user's access by using team profiles. For details, see Configuring Team Profiles.
|Pause job before sending||
This setting determines whether the Connector automatically pauses a job before sending it out for translation, after Preparing status (0%) but before Sending status (1%). This is useful if you want to review or export reports of content items, or download the XML files before sending them out for translation. You can resume a paused job in the Translation Status page.
Note: You can also configure this setting using the PauseBeforeSend property in CRXDE Lite. For details, see Configuring All Jobs to Pause.
|Only Translation Admin can pause jobs||
This setting determines who can use the pause button in the Translation Status page. You can pause a job before sending it out for translation, after Preparing status (0%) but before Sending status (1%). This is useful if you want to review or export reports about XML files with content items, or download the XML files before sending them out for translation.
|Disable default language mapping||
This setting disable Adobe Experience Manager's default language mapping feature.
Note about adaptive forms: If you are sending out adaptive forms for translation, clear this check box to enable Adobe Experience Manager's default language mapping. If you are using custom languages, then in the Language Mapping page, use the Identity column to link your custom languages to the corresponding default Adobe languages. For detailed instructions, see Configuring Connector Languages. This step is required because adaptive forms support only the locales defined in Adobe languages.
|Open linked pages in||
This setting configures whether the Connector opens page-path links in either Adobe Experience Manager's Touch UI or its Classic UI. These page-path links are displayed in the following Connector interfaces:
|Status UI Default Settings||This sub-section determines the default values for UI elements in the Translation Status page.|
|Show jobs from past||
This setting determines the default date range for displaying translation jobs in the Translation Status page. A job's date is its submission date. The supported values are:
Note: In the Translation Status page, the user can use the Period fields and date choosers to change the date range for displayed translation jobs.
|Show jobs submitted by||
This setting determine the default value of the Submitted By dropdown list in the Translation Status page. The supported values are:
Note: The user can change this selection in the Translation Status page.
|Translation Default Settings||
This sub-section determines the default settings of these options when they are displayed in the Bulk Translation wizard, the Translation Queue, the Translate Content page in the Touch-Optimized UI, and in the Sidekick. The Connector also uses these default translation options for catching rollout pages to the Translation Queue, if
the Catch rollout pages to [Rollout] Queue check box is selected in the Translation Settings section of the Configuration page. For all these options:
Note about the Catch rollout pages to [Rollout] Queue feature: If a check box is enabled, then the option is selected. This feature has no user interface for changing the value.
Many of the options in this section are related to Adobe Experience Manager's MSM (Multi Site Manager) and Rollout features. For a description of these features and related concepts, as well as integration with the Connector, see MSM and Rollout Settings.
Note: Depending on your company's configuration, users may not be able to change these values. For example, if the Show options on Bulk UI check box, described above, is not selected, then users cannot change these settings in the Bulk Translation wizard. In that case, this section determines the default value of these settings.
|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.
|Select if using Blueprint/
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.
Recommendation: Select this check box if you are using the live-copy feature.
|Only translate content from locked components||
This option enables users to send out only content from locked components for translation.
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.
|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.
|Allow translated content from Not-Sync 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.
Important: The Connector treats certain page properties (
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.
|Translate Page Content||
Important: To send out words on pages for translation, you must select this option.
The corresponding check box is displayed when sending out content for translation from:
This option enables users to send out for translation metadata fields that are defined in the Page Metadata Configuration section of the Advanced Settings page. For details, see Configuring which Page Metadata is Available for Copying and Translation. These are properties under the /jcr:content node. The corresponding check box is displayed when sending out content for translation from:
|Target Page Revisioning||
This sub-section specifies the settings for the Target Page Revisioning feature. By default, this feature is not enabled. You use this feature to configure the Connector to support editing multiple versions of a source page concurrently. This is useful in scenarios where your publishing cycle is shorter than your translation cycle, because you can retain and publish a previous version of the translated content while the current version of the source content is out for translation. For information on page revisioning in Adobe Experience Manager, refer to the Adobe Experience Manager documentation at: https://helpx.adobe.com/experience-manager/6-5/sites/authoring/using/working-with-page-versions.html.
Important: This feature is relevant and available only when updating existing content, that is, when the target page already exists. If you are creating a new language copy, the Connector does not create a revision, because there is no pre-existing target content.
Recommendation: If you use this feature, an administrator should occasionally purge the version history to reduce the repository size. For more information, refer to the Adobe Experience Manager documentation at https://helpx.adobe.com/experience-manager/6-5/sites/deploying/using/version-purging.html.
Selecting this check box enables the Target Page Revisioning feature, described above.
Note: The page revision name is visible only in Adobe Experience Manager's Classic UI. In Adobe Experience Manager's Touch-Optimized UI, the revision is displayed without a name.
Remove Revisions on Completion
If you select this check box, then after the Connector imports the translated content into Adobe Experience Manager, it removes the Before <job name> and During <job name> revisions, described above. The Connector does not remove the Completed <job name> revision, because this is the target page that has been updated with translated content.
Note: Relevant only if the Use Revisioning check box, described above, is selected. Otherwise, the Connector ignores this setting.
|Restore Target Pages while under Translation||
If you select this check box, then as soon as the Connector sends out content for translation, it restores the Before <job name> revision of the page. This revision contains the previously translated version of the page. If you do not select this check box, then the updated source content that has been sent out for translation is the current target content, which is the default Connector behavior.
Important: Relevant only if the Use Revisioning check box, described above, is selected. Otherwise, the Connector ignores this setting.