This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Sending Content for Translation

When the Connector sends out a page for translation, it actually sends out the components in that page for translation. There are several possible component configurations:

  • a component may be synchronized to a Blueprint page

  • a component may be in a live copy page

  • a component may exist on a page that has no relationship to MSM (Multi Site Manager)

Determine how your components are configured before deciding how to send out pages for translation. The Connector supports multiple ways of sending out pages for translation.

Recommendation: Consult the Adobe Experience Manager documentation to learn about the MSM, Rollout, and translation workflow features. Learn how pages and their components are locked and synchronized. The Connector uses many of these features, and extends them to enable sending pages and their components for translation.

Your system may be configured to use these features in very specific ways. You must be aware of these page relationships and processes before sending content for translation. Otherwise, unexpected outcomes may occur.

There are multiple ways to collect and send content for translation using the Connector:

For an overview and comparison of these methods, see Multiple Ways to Send Content for Translation.

Note about team profiles: If one or more paths are configured for your team profile, you can select only pages and fragments that are in these paths for translation. The path configuration does not restrict your selection of digital assets, tags, and dictionaries (i18n items).

Content Type Method of Sending for Translation
pages all supported methods
tags Bulk Translation wizard only
dictionaries (i18n items) Bulk Translation wizard only
Content Fragments and Experience Fragments Bulk Translation wizard and Globalization Tool only
adaptive forms Bulk Translation wizard and Globalization Tool only
digital assets, such as JPG and PDF files Bulk Translation wizard and Globalization Tool only

The owner of the translation budget can review and approve the content that has been identified as requiring translation, and can send it out for translation. For details, see Submitting Content for Translation from the Translation Queue.

Note: Your company may be configured to automatically send content items for translation to the Translation Queue. Your company may have created schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide or contact your Adobe Experience Manager administrator.

Adobe Experience Manager’s Translation Integration feature

You can also send out content either directly to translation or to the Translation Queue using Adobe Experience Manager’s translation integration feature (TIF).

1 - Sending Content for Translation Using the Bulk Translation Wizard

The Bulk Translation wizard enables you to select, send, and receive large quantities of content for translation in only a few clicks.

This is useful for quickly sending out entire sections, sites, or content trees for translation into one or more languages. Each group of pages you send out for translation is a separate job. You can specify different settings and create a different requested-by date for each job.

You access the Bulk Translation wizard from the Lionbridge Connector rail or directly from your Web browser address bar.

When you use the Bulk Translation wizard, you can submit content either to the Translation Queue or directly to translation.

Notes: You can submit tags and dictionaries (i18n items) for translation only using the Bulk Translation wizard. You can submit Content Fragments, Experience Fragments, and adaptive forms for translation only using the Bulk Translation wizard or the Globalization Tool. You can configure the Connector to submit for translation Content Fragments that are referenced in pages, Experience Fragments, and adaptive forms by selecting the Translate Dependent CF check box in the Translation Settings section of the Configuration page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

Note: Depending on your company configuration, you can submit digital assets, such as PDF and JPG files, for translation, including asset metadata.

Note: Depending on your user permissions or your company configuration, you may not be able to send out content directly for translation.

To send out content for translation via the Bulk Translation wizard, you complete the following steps:
  1. Open the Bulk Translation wizard and specify initial settings in the Settings page of the wizard. For detailed instructions, see Specifying Initial Settings in the Bulk Translation Wizard.

  2. In the Item Type page of the wizard, you specify which content items to send for translation. For detailed instructions, see Selecting Content Items to Translate.

  3. In the Options page of the wizard, you can specify the following options:

    • whether to check the local TM (translation memory) to determine if previously translated source content has been updated
    • if the target pages are MSM (Multi Site Manager) live copy pages, whether to prevent the Connector from overwriting unique source content that already exists in the target pages
    • whether to translate content only from locked components
    • whether to automatically unlock a component after translated content returns
    • whether to send non-synchronized components (without a relationship to a Blueprint page) for translation
    • whether to translate regular content fields in pages
    • whether to send out for translation metadata fields, for pages, that are defined in the Page Metadata Configuration section of the Advanced Settings page
    • whether to save any target content that has already been translated to the local translation memory (TM) instead of sending it out for translation
    • whether to select the Level-2 Queue Metadata analysis code for content items to send for translation

For detailed instructions and descriptions of these options, see Specifying Translation Options.

  1. Optional. If you are sending content directly out for translation (not to the Translation Queue) and If multiple translation providers are configured for your team profile, then in the LSP page of the wizard, you select your translation provider (LSP). If your translation provider is Lionbridge Freeway, you select Freeway-specific options. For detailed instructions, see Selecting Your Translation Provider.

  2. Optional. If you are sending content directly out for translation (not to the Translation Queue), then in the Translation Job page of the wizard, you can specify the following parameters for your translation job:

    • deadline
    • notes for the translation provider
    • reference files (support assets) that provide helpful context for the translator
    • the content type of the content in the translation job
    • request a quote from the translation provider before the translation process starts
    • job name
    • job description
    • purchase order reference number
    • email addresses that will receive notification emails about the status of the translation job
    • localization reviewer

In this wizard page, you also send the translation job to the translation provider you specified earlier.

For detailed instructions, see Specifying Job Options and Submitting Your Job.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

1.1 - Specifying Initial Settings in the Bulk Translation Wizard

To get started, you open the Bulk Translation wizard and specify the source and target languages for the job. If you are a member of multiple teams, you also select the team profile to use in this job.

To send out content for translation via the Bulk Translation wizard:
  1. Do one of the following to open the Bulk Translation wizard:

    • In the Touch-Optimized UI of Adobe Experience Manager, click the Tools icon and then click Lionbridge Connector in the Adobe Experience Manager rail. (This opens the Connector in a new browser tab.) Then, click Bulk Translation in the Lionbridge Connector rail.
    • In the Classic UI of Adobe Experience Manager, scroll down and click Lionbridge Connector in the right pane. Then, click Bulk Translation in the Lionbridge Connector rail.
    • In your Web browser, navigate to /content/ctctranslation/bulktrans.html on your Adobe Experience Manager instance.

The Settings(#) page of the Bulk Translation wizard opens.

  1. In the Settings page, you choose the following settings:
Setting Description
Profile If you are a member of multiple teams, then in the Profile dropdown list, select the team profile to use with the Bulk Translation wizard. This displays the source and target languages and the translation providers specified for the team profile.
Source Language Select the source language for translation. The Connector will send pages in this source language for translation.
Target Language Select the check boxes for all the target languages into which you want to translate the source content. The list displays all the languages that are set up in Adobe Experience Manager for your team. To select all available languages, select the All check box.
Translate/Copy source to target only For each language you select, choose one of the following options:
  • Translate: This creates a copy of all the source nodes and pages in the target. The Connector sends all pages in the source site structure for translation.
  • Copy source to target only: The Connector copies the source content to the target content item without sending it out for translation. This is useful when there is content that you do not want to translate, but that you want to include in the target version.

Note: The Connector creates these pages in the target structure. If pages already exist in the target structure, including previously translated content, the Connector overwrites these pages with the source content.
  1. Click Next.

The Item Type page of the wizard opens. For detailed instructions, see Selecting Content Items to Translate.

1.2 - Selecting Content Items to Translate

After clicking Next in the Settings page of the Bulk Translation wizard, the Item Type page opens.

To select which items to translate:
  1. At the top of the Item Type page, select one of the following item types:

    • Pages: Web pages, Content Fragments, Experience Fragments, adaptive forms, or digital assets.

    • Tags: Metadata assigned to a content item within Adobe Experience Manager (usually a page), which act as keywords or labels attached to that content item.

    • i18n dictionaries: Texts and their translations in a CQ5 Translator dictionary.

  2. In the Search from Site Path field, specify the highest root folder of all source pages, tags, or dictionaries to send for translation. Either:

    • Click the arrow at the end of the field , navigate to that path, select it, and click Select.

Note: By default, the dialog box opens to the path of the root folder for the source language you selected in step 2, above.

  • Type the path in the following format: /content/geometrixx/en. For Content Fragments, or Experience Fragments, type the path in the following format: /content/dam/en. For adaptive forms, type the path in the following format: /content/forms/af.

Tip: Alternatively, you can click Load Saved to load the last set of previously saved page paths to the list.

Note about team profiles: If one or more paths are configured for your team profile, you can select only pages that are in these paths for translation. The path configuration does not restrict your selection of digital assets, tags, and dictionaries (i18n items).

Note: To send digital assets, including their metadata, for translation, the path is under the language root under /content/dam, for example: /content/dam/geometrixx/en/icons.

  1. Optional. In the Modification Filter From field, enter the earliest modification date for which to include items. Enter the date in the YYYY-MM-DD format. In the To field, enter the latest modification date for which to include pages. To apply this filter to the items that the search agent will collect, select the Apply Modification Filter check box. If you use this option, only items that were changed in the specified date range are included.

  2. In the Search Using Agent field, select an agent to collect items to send for translation. Select a custom agent or one of the following pre-configured agents from the list:

    • Page agents, which are available only if Pages is selected in Item Type, at the top of the page:

      • Get current page: Default. The agent collects the root page of the path specified in the Search from Site Path box, above.

      • Get all children pages: The agent collects all children pages of the path specified in the Search from Site Path box, above. It does not collect any pages in the root path.

      • Get current page and all children pages: The agent collects the root page and all children pages of the path specified in the Search from Site Path box, above.

    • The Get current and child tags agent, which is available only if Tags is selected in Item Type, at the top of the page.

    • The Get i18n agent, which is available only if i18n dictionaries is selected in Item Type, at the top of the page.

Note: For information on creating a custom agent, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

  1. Click Add.

The specified agent collects all items that match the search criteria and displays them in the list. By default, the check box for each page you add is selected, and the check box for each tag or i18n dictionary is cleared.

The following summary information is displayed:

  • Total Displayed: The total number of items available for selection.

  • Total Selected (for translation): The number of items selected to send out for translation.

The following information is displayed about each item:

Column Description
Path The path to the item to send out for translation.
Tip: Click the link to open the page, fragment, or form in a new browser tab. The page opens in either the Touch UI or the Classic UI, depending on your company’s configuration.
Content The type of content to send out for translation. Supported values are all the types of nodes included in your company’s website.
- dam:Asset [CF] is displayed for Content Fragments.
- cq:Page [XF] is displayed for Experience Fragments.
- cq:Page [AF] is displayed for adaptive forms.
Template The Adobe Experience Manager template used to create the item.
Modification - The date and time when the item was last modified, in the following format: YYYY-MM-DD kk:mm:ss, where kk is the hour represented by a 24-hour clock.
- The (m) following the date and time indicates that the item was modified. The username of the user who last modified the item is displayed in parentheses, for example, [admin].

Note: You can repeat steps 5 to 8 to perform multiple searches and add multiple sets of items with different root folders to the list of items to translate. However, all sets of items must be of the same type, such as page items.

Note: You can select one dictionary item at a time for translation. To select another dictionary item for translation, run the Bulk Translation wizard again.

  1. Optional. You can click the Toggle Filter link to display a text box at the top of the list. As you type into the this text box, the Connector automatically filters the list of page and asset paths and names and displays only the matching items.

  2. Clear the check boxes of any items you do not want to send out for translation. Ensure that the check boxes are selected for any items you want to send out for translation.

  3. Use the following features to modify the list of items to send out for translation:

    • To select the check boxes for all the items in the list, click Select All.

    • To clear the check boxes for all the items in the list, click Unselect All.

    • To remove all the items from the list, even if the corresponding check boxes are selected, click Clear.

  4. Optional. To save the page paths displayed in the list, so that you can reload them later, click Save.

  5. Optional. To update the Total Selected (for translation) field above with the number of items with selected check boxes, click Update.

  6. Click Next.

The Options page of the wizard opens. For detailed instructions, see Specifying Translation Options.

1.3 - 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:

1.4 - Selecting Your Translation Provider

After clicking Next in the Options page of the Bulk Translation wizard, if multiple translation providers are configured for your team profile, the LSP page of the wizard opens. In this page, you select your translation provider (LSP) and configure any LSP-specific options.

To select your translation provider:
  1. In the Choose LSP list, select the translation provider for this translation job from the list.

  1. If you selected Lionbridge Freeway in the previous step, complete the following additional fields:
Field Description
Special Instruction Any additional instructions for Freeway, which are sent as metadata. Available only if the selected translation provider in the Choose LSP box, above, is the Lionbridge Freeway Type.
Analysis Code The Freeway analysis codes for the translation. Displayed only if:
- In the Choose LSP box, above, the selected provider is the Lionbridge Freeway Type.
- The Connector is configured to display these fields.
You specify the analysis codes that are relevant to your content. Your Lionbridge setup determines which analysis codes are available for you to specify, and the values available for selection for each analysis code. For example, the Region, Department, and Priority analysis codes may be available for you to specify.
  1. Click Next.

The Translation Job page of the wizard opens. For detailed instructions, see Specifying Job Options and Submitting Your Job.

1.5 - Specifying Job Options and Submitting Your Job

Specifying Job Options and Submitting Your Job

The Translation Job page of the Bulk Translation wizard opens when:

  • You click Next in the Options page of the wizard, if multiple translation providers are not configured for your team profile.
  • You click Next in the LSP page of the wizard, if multiple translation providers are configured for your team profile.
To specify job options and submit your job for translation:
  1. In the Translation Job page of the wizard, enter the following information about the files to send out for translation:

Option Description
Deadline The date you are requesting for the translated content to return. Click in the field and select a date in the calendar that opens. This information is sent to the translation provider as metadata of the translation package.

Recommendation: Discuss whether to use this feature with your translation provider(s).
Translation Notes Enter any additional information about this translation job. This information is sent to the translation provider as a comment in the metadata of the translation package.
Reference Files You can send reference files (support assets) to your translation provider as part of a translation job. This provides helpful context for the translator.

For instructions on adding reference files in Adobe Experience Manager, refer to the Adobe Experience Manager documentation for uploading digital assets:

* version 6.2: https://helpx.adobe.com/experience-manager/6-2/assets/using/managing-assets-touch-ui.html
* version 6.3: https://helpx.adobe.com/experience-manager/6-3/assets/using/managing-assets-touch-ui.html
* version 6.4: https://helpx.adobe.com/experience-manager/6-4/assets/using/managing-assets-touch-ui.html
* version 6.5: https://helpx.adobe.com/experience-manager/6-5/assets/using/managing-assets-touch-ui.html

**Note:** This feature is available only if the **Allow Reference Files for Translation Job** check box is selected in the **UI and Default Settings** section of the **Configuration** page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

##### To add a reference file to the Connector:

1. Click the down arrow and navigate to the reference file or folder containing reference files.
2. Select the reference file or folder containing reference files and click **Select.**
3. Repeat the previous steps for each reference file or folder containing reference files that you want to include.

The Connector will send all specified files and all files in the specified folders to the translation provider.
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:

* Marketing
* Technical
* Legal

**Note:** You may see different content types if your company has configured custom content types.
Quote Select this check box to inform the translation provider that you want to receive a quote before the translation process starts.

Note: This check box is displayed only if the selected translation provider is configured to support providing a quote before the translation process starts.
Job Name Your name for this translation job. By default this includes the username, date, and time when you created the job, for example: Submit by [admin] @ 2016-12-20 6.57 PM. This is stored in the CQJobName attribute in the XML that the Connector sends to the translation provider.
PO Reference Enter the purchase order reference number.
Job Description Additional information about this job. This is stored in the CQJobDescription attribute in the XML that the Connector sends to the translation provider.
Notification Emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.
In-country Reviewer Optional. This is generally the name of the localization reviewer, which is stored in the InCountryReviewer attribute in the XML sent to the translation provider. By default, this field is hidden.

Note: If you want to send the selected items to the Translation Queue instead of sending them out directly for translation, click Add to queue. The Translation Queue opens. For details, see Submitting Content for Translation from the Translation Queue.

  1. Click Start Translation.

The Connector sends the translation job to the translation provider you specified.

The Job Details tab of the Translation Status page opens, where you can monitor the progress of your translation job. For details, see Monitoring Pages in a Translation Job and Viewing Translated Content.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

2 - Sending Pages for Translation Using the Globalization Tool

The Globalization Tool enables you to send multiple pages, digital assets, Content Fragments, Experience Fragments, and adaptive forms directly out for translation or to the Translation Queue. You can add pages from multiple site paths, and/or upload paths stored in CSV or XLS files. You can filter pages and assets by publication date, on time, off time, activation state, and page template.

Important: By default, this feature is hidden. To use the Globalization Tool, you must select the Show Globalization Tool check box in the UI and Default Settings section of the Configuration page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

Notes: You can submit Content Fragments, Experience Fragments, and adaptive forms for translation only using the Bulk Translation wizard or the Globalization Tool. You can configure the Connector to submit for translation Content Fragments that are referenced in pages, Experience Fragments, and adaptive forms by selecting the Translate Dependent CF check box in the Translation Settings section of the Configuration page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

Note: Depending on your company configuration, you can submit digital assets, such as PDF and JPG files, for translation, including asset metadata.

You can also use the Globalization Tool to perform Adobe Experience Manager actions on multiple pages and digital assets simultaneously. For detailed instructions, see Performing Actions on Multiple Pages and Digital Assets.

To send out pages and assets for translation via the Globalization Tool:
  1. Do one of the following to open the Globalization Tool:

    • In the Touch-Optimized UI of Adobe Experience Manager, click the Tools icon and then click Lionbridge Connector in the Adobe Experience Manager rail. (This opens the Connector in a new browser tab.) Then, click Globalization Tool in the Lionbridge Connector rail.

    • In the Classic UI of Adobe Experience Manager, scroll down and click Lionbridge Connector in the right pane. Then, click Globalization Tool in the Lionbridge Connector rail.

    • In your Web browser, navigate to /content/ctctranslation/advbulk.html on your Adobe Experience Manager instance.

The Globalization Tool opens.

  1. Optional. If you are a member of multiple teams, then in the Profile dropdown list, select the team profile to use with the Globalization Tool. This displays the source and target languages and the translation providers specified for the team profile. To always use the selected profile with the Globalization Tool, click Set as default.

  2. In the Select Pages section, you either set the parent path of one or more files to upload, apply filters, and then use an agent to upload the files, or you upload one or more files containing the paths of pages. You repeat this step until you have added all the paths and files to add. Do one of the following to select pages:

    • To set the parent path of one or more files to upload, apply filters, and then use an agent to upload the files:

Note about team profiles: If one or more paths are configured for your team profile, you can select only pages that are in these paths for translation. The path configuration does not restrict your selection of digital assets.

a. In the Search from Site Path field, specify the highest root folder of all source pages or the full path of a page of a website. Either:

  • Click the arrow at the end of the field , navigate to that path, select it, and click Select.

  • Type the path in one of the following formats: /content/geometrixx/en or http://localhost:4502/content/geometrixx/en/company.html. For Content Fragments, or Experience Fragments, type the path in the following format: /content/dam/en. For adaptive forms, type the path in the following format: /content/forms/af.

Note: To send digital assets, including their metadata, for translation, the path is under the language root under /content/dam, for example: /content/dam/geometrixx/en/icons.

Tips: You can select a previously entered path. Alternatively, you can click Load Saved to load the last set of previously saved page paths to the list.

b. Optional. Specify any of the following filters:

Filter Description How To Specify…
Modification Filter The range of dates when the page was modified. * In the From and To boxes, enter the dates in YYYY-MM-DD format.
* Select the **Apply modification filter** check box.
Publishing Filter The range of dates when the page was published. * In the From and To boxes, enter the dates in YYYY-MM-DD format.
* Select the **Apply publishing filter** check box.
Off time (expiration) The range of dates when the page was off time, or unpublished. * In the From and To boxes, enter the dates in YYYY-MM-DD format.
* Select the **Apply offtime filter** check box.
On time The range of dates when the page was on time. * In the From and To boxes, enter the dates in YYYY-MM-DD format.
* Select the **Apply ontime filter** check box.
Page template filter The Adobe Experience Manager template used to create the page. Select the check boxes for the templates to include, or select the check box in the list header to include all templates.

Tip: For precise descriptions of some of these terms, refer to the Adobe Experience Manager documentation, available at: https://docs.adobe.com/docs/en/aem/6-2/author/page-authoring/publishing-pages.html.

c. Optional. In the Page activation state section, select one or more of the following activation states for the pages to include:

  1. Activated: The page has been activated (published).
  2. DeActivated: The page was activated (published) and then deactivated (unpublished).
  3. Never Activated: The page has never been activated (published).

d. In the Search Using Agent field, select an agent to collect items to send for translation. Select a custom agent or one of the following pre-configured agents from the list:

  • Get current page: Default. The agent collects the root page of the path specified in the Search from Site Path box, above.
  • Get all children pages: The agent collects all children pages of the path specified in the Search from Site Path box, above. It does not collect any pages in the root path.
  • Get current page and all children pages: The agent collects the root page and all children pages of the path specified in the Search from Site Path box, above.

e. Click Add.

You can repeat these steps to add multiple sets of pages with different root folders to the list of pages.

  • To upload a file with the paths of the source content or import pages from a previously sent translation job, click the Load pages button:

Note: If an optional package is installed, you can upload an Excel file with the target languages for a translation job. For a description of the required formatting in the Excel file, see Importing Target Languages in the Globalization Tool. To obtain this optional package, contact Lionbridge Connector Support.

The Select a file to upload dialog box opens.

Do one of the following:

  • To upload a file with the paths of the source content:

    a. Click Choose File.

f. In the browser dialog box that opens, navigate to the XLS or CSV file containing the paths of the source files, select it, and click Open, or similar, to close the browser dialog box.

The Select a file to upload dialog box displays the path of the file you selected.

g. Click Upload to upload the file.

A message box confirms that the file is added.

h. Click OK to close the message box.

The specified agent collects all items that match the search criteria and adds them to the list. You can repeat these steps to add additional files containing paths of pages to the list.

  • To import pages from a previously sent translation job:

a. In the Import pages from translation job – From dropdown list, select the time range of previous translation jobs to display. The default value is Last two weeks.

b. Click the Refresh icon to populate the list of previous translation jobs in the list below.

c. Select the previous translation job to import from the dropdown list at the bottom of the dialog box.

d. Click Import.

The Connectors adds the content items from the selected job to the list.

The following summary information is displayed in the Pages x/y field, where:

  • X is the total number of pages available for selection.
  • Y is the number of pages selected to send out for translation.

The following information is displayed about each page:

Column Description
blank A locked padlock icon indicates if the page is locked.
Path The path to the page.

Tip: Click the link to open the page, fragment, or form in a new browser tab. The page opens in either the Touch UI or the Classic UI, depending on your company’s configuration.
Lng The Adobe Experience Manager language of the page.
Loc The Adobe Experience Manager locale of the page.
Template The Adobe Experience Manager template used to create the page.

* dam:Asset [CF] for Content Fragments
* cq:Page for Experience Fragments
* cq:Page [AF] for adaptive forms
T. Status Optional. The custom translation status configured for the translation provider (LSP) that translated the page.

Note: This column is displayed only if custom translation-status values are configured. For instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.
Activation Whether the page is activated or deactivated.
Activation/De-Activation Date * The date and time when the page was last activated or de-activated, in the following format: YYYY-MM-DD kk:mm:ss, where kk is the hour represented by a 24-hour clock.
* The username of the user who activated or deactivated the page.
* One of the following codes, indicating whether the page was last activated or de-activated:
* CTA: Activated
* CTD: Deactivated.
Modification * The date and time when the item was last modified, in the following format: YYYY-MM-DD kk:mm:ss, where kk is the hour represented by a 24-hour clock.
* The (m) following the date and time indicates that the item was modified. The username of the user who last modified the item is displayed in parentheses, for example, [admin].
* One of the following codes, indicating how the page was last modified:
* CTT: Translation
* CTU: Update
* CTI: Import
* CTR: Rollout
  1. Select the check boxes for any pages you want to send out for translation. Ensure that the check boxes are cleared for any pages you do not want to send out for translation.

    • To update the numbers of selected pages, highlighted pages, and total pages at the top-left corner of the list, click Re-Count.

    • The number after the check box displays the number of selected pages.

    • The number after the highlight displays the number of highlighted pages.

    • The number after the slash ( / ) displays the total number of pages.

For example:

  • To select the check boxes for all the pages in the list, click Select All.
  • To clear the check boxes for all the pages in the list, click De-Select all.
  1. Optional. Use the following features to update the list:

    • To remove all the pages from the list, even if the corresponding check boxes are selected, click Clear.

    • To update information about pages displayed in list, such as modification date, click Refresh.

  2. Optional. To save the page paths displayed in the list, so that you can reload them later, click Save.

  3. Optional. To view a page, click the path in the Path column. The page opens in a new browser tab.

  4. In the Translation tab, specify the translation settings for the selected pages in the list.

Note: For a description of all other tabs, see Performing Actions on Multiple Pages and Digital Assets.

Setting Description
Source language Select the source language for translation. The Connector will send pages in this source language for translation.
Target language Select the check boxes for all the target languages into which you want to translate the source content. The list displays all the languages that are set up in Adobe Experience Manager for your team.

* To select the check boxes for all available languages, click **All**.
* To clear all selected check boxes, click **Clear**.
Deadline The date you are requesting for the translated content to return. Click in the field and select a date in the calendar that opens. This information is sent to the translation provider as metadata of the translation package.

Recommendation: Discuss whether to use this feature with your translation provider(s).
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.
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.
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.
Notes Enter any additional information about this translation job. This information is sent to the translation provider as a comment in the metadata of the translation package.
MSM Options
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.
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.
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.
Allow translate 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.

* 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.
  1. Do one of the following:

    • If you want to send the selected items to the Translation Queue instead of sending them out directly for translation, click Add to Queue. The Translation Queue opens. For details, see Submitting Content for Translation from the Translation Queue.

    • To immediately send out the selected items for translation as a single translation job, you must enter the following information in the Send for Translation Now section:

a. In the Choose LSP dropdown list, select your translation provider (LSP). If you select Lionbridge Freeway, the section expands to display additional fields.

b. Enter the following information about your translation job:

Setting Description
Special Instruction Any additional instructions for Freeway, which are sent as metadata. Available only if the selected translation provider in the Choose LSP box, above, is the Lionbridge Freeway Type.
Analysis Code The analysis codes for the translation. Displayed only if Lionbridge Freeway is selected in the Choose LSP box, above.

You specify the analysis codes that are relevant to your content. Your Lionbridge setup determines which analysis codes are available for you to specify, and the values available for selection for each analysis code. In this example, the Color, Direction, and Sense analysis codes are available for you to specify.
Translation job name Your name for this translation job. By default this includes the username, date, and time when you created the job, for example: Submit by [admin] @ 2016-12-20 6.57 PM. This is stored in the CQJobName attribute in the XML that the Connector sends to the translation provider.
Job description Additional information about this job. This is stored in the CQJobDescription attribute in the XML that the Connector sends to the translation provider.
Reference Files You can send reference files (support assets) to your translation provider as part of a translation job. This provides helpful context for the translator.

For instructions on adding reference files in Adobe Experience Manager, refer to the Adobe Experience Manager documentation for uploading digital assets:

* version 6.2: https://helpx.adobe.com/experience-manager/6-2/assets/using/managing-assets-touch-ui.html
* version 6.3: https://helpx.adobe.com/experience-manager/6-3/assets/using/managing-assets-touch-ui.html
* version 6.4: https://helpx.adobe.com/experience-manager/6-4/assets/using/managing-assets-touch-ui.html
* version 6.5: https://helpx.adobe.com/experience-manager/6-5/assets/using/managing-assets-touch-ui.html

**Note:** This feature is available only if the **Allow Reference Files for Translation Job** check box is selected in the **UI and Default Settings** section of the **Configuration** page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

##### To add a reference file to the Connector:

1. Click the down arrow and navigate to the reference file or folder containing reference files.
2. Select the reference file or folder containing reference files and click **Select**.
3. Repeat the previous steps for each reference file or folder containing reference files that you want to include.

The Connector will send all specified files and all files in the specified folders to the translation provider.
PO Reference The purchase order reference number for this translation job.
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:

* Marketing
* Technical
* Legal

**Note:** You may see different content types if your company has configured custom content types.
Quote Select this check box to inform the translation provider that you want to receive a quote before the translation process starts.

Note: This check box is displayed only if the selected translation provider is configured to support providing a quote before the translation process starts.
Notification emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.
  1. Click Start translation.

The Connector sends the translation job to the translation provider you specified.

The Job Details tab of the Translation Status page opens, where you can monitor the progress of your translation job. For details, see Monitoring Pages in a Translation Job and Viewing Translated Content.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

2.1 - Importing Target Languages in the Globalization Tool

You can upload a Microsoft Excel file with a list of target languages when sending out files for translation from the Globalization Tool, as described in Sending Pages and Assets for Translation Using the Globalization Tool.

Microsoft Excel file format

The Microsoft Excel file must have the following format:

Excel Column Column Header Notes
A GEP
B Project Name
C Channel
D Sub Channel
E Assets
F Cycle Name
G Production Status
H Source Word Count
I Translated Word Count
J Total Cost
K Total Project Cost
L Markets Target languages and codes, comma separated, for example: English(EN-GB), French(FR-CA)
M HODate
N HBDate
O Actual Final HB
P Desired HBDate
Q Actual Localization Complete Date
R Daily Comments
S Field Review Start Date
T Field Review Complete Date
U Total Number of Language
V Delayed Language
W Total Number of delayed Days
X Total Number of delayed Language
Y Average Delay
Z Query
AA File Location
To upload the Excel file:
  1. Click the Load pages button to open the Select a file to upload dialog box.

  2. In the dialog box, browse to and select the Excel file, and click Open, or similar, to close the browser dialog box. The Select a file to upload dialog box displays the path of the file you selected.

3 - Sending Files to the Translation Queue When You Roll Out Files

If your Connector is appropriately configured, then when you roll out files, the Connector automatically sends them to the Translation Queue using your company’s default translation settings.

For more information about this feature, read:

This feature is available only if either the CTCRolloutTranslation workflow is part of your rollout configuration, or the Catch rollout pages to [Rollout] Queue check box in the Translation Settings section of the Configuration page is selected. For more information on configuring this feature, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

3.1 - Adobe Experience Manager's MSM and the Rollout Process

Adobe Experience Manager includes the powerful Multi Site Manager (MSM), which facilitates managing multiple versions of web sites. The versions may be region specific, for example, a car company may have a different English version of its web site for each English-speaking country where it sells cars. Typically, one version of the site is considered the “source” site. Content in each target website may have different kinds of relationships to the version in the “source” site:

  • Some content may be common to all web sites, such as the car company’s history.
  • Some content may be a mix of common and specific. For example, the company may sell the same cars in many countries, but the cars may have slightly different features in some countries, depending on local regulations.
  • Some content may be specific to a specific version of the site, such as information about car dealerships in a particular country.

Rollout is a process that propagates the changes made from the source (Blueprint) to the target (live copy). When you roll out a site, Adobe Experience Manager copies the Blueprint (source) to the live copy (target). If the components are locked, then whenever the source content changes, Adobe Experience Manager automatically updates the target content.

The following Adobe Experience Manager concepts are helpful to understanding MSM and rollout, and how to configure and use the Connector accordingly:

Concept Description
Blueprint A source template for multiple pages, which can be rolled out.
Live copy A copy of an existing page or Blueprint, which is the target. Adobe Experience Manager can automatically update the live copy when changes occur to the source.

Important: If you use this feature, you must select the Select if using Blueprint/Live-copy option. The Allow translate content from Not-Sync components setting is optional.
Locked Specifies the inheritance relationship between the target and the source. When the source changes, Adobe Experience Manager automatically updates a locked component in the target. In the car company example, this is useful for pages that have the same content in all versions, such as information about the history of the company.
Unlocked Specifies the inheritance relationship between the target and the source. When the source changes, Adobe Experience Manager does not update an unlocked component in the target. In the car company example, this is useful for regionalized pages that should not be updated, such as a list of local car dealerships.

For more information about these features and the rollout process, refer to the Adobe Experience Manager user documentation, available at: https://helpx.adobe.com/experience-manager/6-4/sites/administering/using/msm-sync.html

3.2 - Why Integrate the Connector with Rollout

The Connector extends the MSM functionality by adding the translation component to the rollout feature. This facilitates using rollout not only to manage multiple region-specific sites, but also to manage multiple language-specific sites. The following table describes the advantages of using the Connector with rollout:

Using Rollout Not Using Rollout
Process Roll out pages, which automatically sends them to the Translation Queue. 1. Roll out a same-language version.
2. Translate copied version.
Number of steps One step. Two steps.
link between source and content Source and target can be linked, so when source is updated, changes are automatically sent to the Translation Queue. No linkage between source and target.

3.3 - How the Connector Fits into MSM and Rollouts

The Connector does not have its own user interface during rollout: when you roll out content, you use Adobe Experience Manager’s rollout interface. The Connector manages the translation during the rollout based on your company’s settings for the following options:

  • Only translate content from locked components
  • Select if using Blueprint/Live-copy
  • Unlock the component after translated content come back
  • Allow translated content from Not-Sync’d components

For information on configuring these options, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

  1. Access the Rollout feature in one of the following ways:

    • To roll out one or more pages, in the Blueprint Control Center, navigate to the top-level page in the source language to roll out, and select Rollout from the context menu.

    • To roll out specific components on a page, in Sidekick, in the Page tab, click the Rollout Page button.

  1. Specify which pages or components to roll out.

Select the check boxes corresponding to the live copy path for the target languages to roll out.

  1. Click Rollout.

The Connector automatically sends the specified content to the Translation Queue. After translation, the translated content will be the target content.

After the content is in the Translation Queue, either:

  • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.
  • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

For detailed instructions on using the rollout feature and accessing the Blueprint Control Center, refer to the Adobe Experience Manager user documentation, available at: https://helpx.adobe.com/experience-manager/6-5/sites/administering/using/msm.html.

4 - Sending Pages for Translation from the Touch-Optimized UI (Adobe Experience Manager version 6.3 and higher only)

If you are using Adobe Experience Manager version 6.3 or higher, you can send pages for translation or to the Translation Queue directly from the Touch-Optimized UI.

Tip: This method is ideal for ad-hoc translations or for sending small amounts of content for translation.

Note: Depending on your user permissions or your company configuration, you may not be able to send out content directly for translation.

Note: If one or more paths are configured for your team profile, you can send only pages that are in those paths for translation.

To send pages for translation from the Touch-Optimized UI:
  1. In the Adobe Experience Manager Touch-Optimized UI, navigate to one of the following pages:

    • the page you want to send for translation
    • the parent page of sub pages you want to send for translation
  2. Select the Edit mode. For detailed instructions, refer to the Adobe Experience Manager documentation, “Editing Page Content” which is available at: https://docs.adobe.com/docs/en/aem/6-3/author/page-authoring/editing-content.html.

  3. In the top-left corner, click the Page Information icon .

  4. In the menu that opens, click Translate Content, which is the second-to-last menu option.

The Pages and languages tab of the Translate Content wizard opens.

  1. In this tab, you choose the following settings:
Setting Description
which pages to translate By default, Current page is selected, which sends only the current page for translation. Alternatively, you can select one of the following options from the dropdown menu:

* All sub pages: The Connector sends all sub pages of the current page for translation. It does not send the current page for translation.
* Current page and all sub pages: The Connector sends the current page and all sub pages of the current page for translation.
Source language Select the source language for translation. The Connector will send pages in this source language for translation.
Select all target language(s) Select the check boxes for all the target languages into which you want to translate the source content. The list displays all the languages that are set up in Adobe Experience Manager for your team. To select all available languages, select the Select all target language(s) check box, above the list of languages.
  1. Click the Translation Options tab.

In this tab, you specify the following 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.
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.
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.
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.
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.
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.
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.
  1. If multiple translation providers (LSPs) are defined for your team profile, and if you want to send the specified pages immediately out for translation (rather than to the Translation Queue), then click the LSP tab.

Note: The LSP tab is displayed only if multiple translation providers (LSPs) are configured for your team profile.

In the dropdown list, select the translation provider for this translation job.

  1. Click the Translation tab.

In this tab, you decide to either send the selected pages to the Translation Queue, or to send them out directly for translation as a single translation job.

  • If multiple translation providers are configured for your team profile, then you selected the translation provider in the LSP tab of this page, as described in the previous step.

  • If one translation provider is configured for your team profile, then that is the translation provider to whom the Connector sends your translation job.

Select one of the following options:

  • Add to queue: The Connector adds the specified pages to the Translation Queue. After the pages are in the Translation Queue, either:

    • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.
    • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.
  • Send as a new job: The Connector immediately sends out the specified pages for translation as a new translation job, according to your company’s routing rules and the options you specify below.

Note: This option is available only to users with permission to send pages directly out for translation.

If you decide to send the pages out for translation, then you also specify the translation job options.

Note: The following settings are relevant and available only if you select Send as a new job, above.

Setting Description
how to process pages Select one of the following methods for the Connector to process the selected pages:

* Add to queue: The Connector sends the selected pages to the Translation Queue. This is the default value.
* Send as a new job: The Connector sends the selected pages to the translation provider specified in the **LSP** tab.
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:

* Marketing
* Technical
* Legal

Note: You may see different content types if your company has configured custom content types.
Send for quote first Select this check box to inform the translation provider that you want to receive a quote before the translation process starts.

Note: This check box is displayed only if the selected translation provider is configured to support providing a quote before the translation process starts.
Job Name Your name for this translation job. By default this includes the username, date, and time when you created the job, for example: Submit by [admin] @ 2016-12-20 6.57 PM. This is stored in the CQJobName attribute in the XML that the Connector sends to the translation provider.
PO Reference Enter the purchase order reference number.
Job Description Additional information about this job. This is stored in the CQJobDescription attribute in the XML that the Connector sends to the translation provider.
Notification Emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.
  1. Click Submit.

The Connector sends the translation job to the translation provider you specified. A message box at the top of the page indicates that the pages were sent to the translation provider or the Translation Queue.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

Tip: You can monitor the progress of your translation job in the Job Details tab of the Translation Status page. For details, see Monitoring Pages in a Translation Job and Viewing Translated Content.

5 - Submitting Content for Translation from the Translation Queue

The goal of the Translation Queue is to control translation costs and the translation process. This design assumes that the person with the authority to send content for translation from the Translation Queue manages the translation budget of the organization.

You can send out one, multiple, or all items from the Translation Queue at one time.

Note: Your company can create schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

You submit content for translation from the Translation Queue in the following scenarios:

Note: You can send out pages, tags, and dictionaries (i18n items) for translation using the Bulk Translation wizard. This is the only way to send out tags and dictionaries (i18n items) for translation.

Submitting content to the Translation Queue before sending it out for translation has the following advantages:

  • You may not want to send out each page individually as soon as you finish reviewing it. The Translation Queue facilitates your management of reviewed pages, so that you do not forget about sending individual reviewed pages for translation.

  • Your translation provider may prefer receiving fewer but larger batches of items to translate, rather than individual pages, as it facilitates project preparation, resource assignment, and file analysis.

  • If you want to translate many items into multiple languages, but you want to translate into only one target language at a time, this is a good way to manage that process.

  • The Translation Queue manager may want to route jobs to certain translation providers.

  • The Translation Queue manager may want to add job-specific metadata, such as a purchase order number.

If you or your colleagues have added items to the Translation Queue, you must access it and approve the items you want to send out.

Note: If you do not approve items in the Translation Queue, the Connector does not send them out for translation.

To submit one or more pages from the Translation Queue for translation:
  1. Do one of the following to open the Translation Queue:
  • In the Touch-Optimized UI of Adobe Experience Manager, click the Tools icon and then click Lionbridge Connector in the Adobe Experience Manager rail. (This opens the Connector in a new browser tab.) Then, click Translation Queue in the Lionbridge Connector rail.

  • In the Classic UI of Adobe Experience Manager, scroll down and click Lionbridge Connector in the right pane. Then, click Translation Queuein the Lionbridge Connector rail.

  • In your Web browser, navigate to /content/ctctranslation/queue.html on your Adobe Experience Manager instance.

The Translation Queue displays all the items that were sent to the queue and that have not yet been sent out for translation.

  1. Optional. In the dropdown list boxes above the list of content items, you can filter which items are displayed in the list:
  • Metadata: When selected, the list displays only items with the selected Level-2 Queue Metadata analysis code. This analysis code was specified when the items were submitted to the queue from the Bulk Translation wizard.

Note: Available only when using the Content API Translation Connector for Lionbridge Freeway.

  • From: In the dropdown list, select how the items were submitted to the Translation Queue. The submission type is one of the following:

    • Bulk Wizard: The items (including pages, i18n dictionaries, and tags) were submitted to the queue from the Bulk Translation wizard.

    • Globalization Tool: The pages were submitted to the queue from the Translation tab of the Globalization Tool.

    • Bulk Wizard + Globalization Tool: The items were submitted to the queue from the Bulk Translation wizard or from the Translation tab of the Globalization Tool.

    • Sidekick: The pages were submitted to the queue from the Sidekick.

    • Touch-Optimized UI: The pages were submitted to the queue from the Translate Content page in Adobe Experience Manager’s Touch-Optimized UI.

    • Experience Manager TIF: The pages were submitted to the queue from Adobe’s Translation Integration Framework (TIF).

    • Rollout Workflow Process: The pages were submitted to the queue by the CTCRolloutTranslation workflow, which is part of your company’s rollout configuration.

    • Rollout Event: The pages were submitted to the queue from a rollout event, based on your company’s rollout configuration.

    • Rollout (Workflow + Event): The pages were submitted to the queue by the CTCRolloutTranslation workflow, which is part of your company’s rollout configuration, or from a rollout event, based on your company’s rollout configuration.

    • Publish Workflow Process: The pages were submitted to the queue by the Add Published Page to Translation Queue step in your workflow, based on your company’s Connector configuration.

    • Publish Events: The pages were submitted to the queue from a publish event, based on your company’s Connector configuration.

    • Publish (Workflow + Event): The pages were submitted to the queue by the Add Published Page to Translation Queue step in your workflow, based on your company’s Connector configuration, or from a publish event, based on your company’s Connector configuration.

The list automatically updates and displays only the specified items submitted to the queue with the specified method.

  • Type: In the dropdown list, select the type of items to display. This is one of the following:

    • Pages: Web pages, Content Fragments, Experience Fragments, adaptive forms, or digital assets.

    • Tags: Metadata assigned to a content item within Adobe Experience Manager (usually a page), which act as keywords or labels attached to that content item.

    • i18n Dictionaries: Texts and their translations in a CQ5 Translator dictionary.

    • TIF Assets: Translation files packaged and sent to the Translation Queue by Adobe’s Translation Integration Framework (TIF). These files are packaged in Adobe Experience Manager TIF’s own format.

  • Target: In the dropdown list, select the target language specified in the translation request. In the dropdown list, target languages for translations in the queue are displayed in black. Target languages that are set up in the system, but that are not specified in translations currently in the queue, are displayed in grey, and they are not available for selection. The list automatically updates and displays only items with the specified requested target language.

Tip: This is useful if you want to send out only items for translation to a specific target language.

The following information is displayed about items in the Translation Queue:

Column Description
Page The path and name of the item or fragment to send for translation.

Tip: Click the link to open the page, fragment, or form in a new browser tab. The page opens in either the Touch UI or the Classic UI, depending on your company’s configuration.
Source The language code of the source language of the item to send for translation.
Target(s) The language codes of the target languages into which to translate the content item.
Created On The date and time when the item was created, in the following format: MM/DD/YYYY h:mm AA, where AA is two upper-case characters reflecting a.m. (after midnight) or p.m. (after noon).
User The username of the user who submitted this item to the Translation Queue.
Deadline The requested date for receiving the translated item back from the translation provider, in the following format: MM/DD/YYYY.
Metadata The Level-2 Queue Metadata analysis code specified for this item when it was added to the Translation Queue.

Note: Displayed only when using the Content API Translation Connector for Lionbridge Freeway.
Content In Target Indicates whether the Select if using Blueprint/Live-copy option is specified for this item (relevant only to page items).

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.
  • If this column has a value of Yes, the Connector does not overwrite unique source content that already exists in the target pages.
  • If this column is blank, the Connector does overwrite unique source content that already exists in the target pages.
Translate Locked Indicates whether the Translate Locked Content/Only translate content from locked components option is specified for this item (relevant only to page items).

This option enables users to send out only content from locked components for translation.
  • If this column has a value of Yes, users can send out content for translation only if it is from a locked component.
  • If this column is blank, users can send out content for translation whether or not it is from a locked component.
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.
Translate Not-Sync’d Indicates whether the Translate Non-Sync’d Components/Allow translated content from not-sync’d components option is specified for this item (relevant only to page items).

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 column has a value of Yes, users can send out content for translation if it does not have a relationship to a Blueprint page.
  • If this column is blank, users cannot send out content for translation if it does not have a relationship to a Blueprint page.
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.
Leave Unlocked Indicates whether the Unlock When Done/Unlock the component after translated content come back option is specified for this item (relevant only to page items).

This option automatically unlocks a component after translated content returns.
  • If this column has a value of Yes, the Connector automatically unlocks a component after translated content returns.
  • If this column is blank, the Connector does not automatically unlock a component after translated content returns.
Translate Page Content Indicates whether to translate regular content fields in this content item.

Important: To send out words on pages for translation, this column must display Yes.
Translate Metadata Indicates whether to translate metadata fields in this content item. The metadata fields are configured in the Page Metadata Configuration section of the Advanced Settings page. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.
Use Local TM Indicates whether the Use Local TM option is specified for this item.

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 column has a value of Yes, the Connector checks whether content was already translated before sending it out for translation.
  • If this column is blank, the Connector sends out content for translation without checking whether it has already been translated.
Words The number of words in the file to translate. This does not include any words that were already translated if the Use Local TM check box is selected. That word count is displayed in the Use Local TM column, described above.

Note: The number of words in digital assets, such as JPG or PDF files, is not displayed.
Counted Indicates whether the Connector counted the words in this content item. This is one of the following:
  • 1: The Connector counted the words in this content item.
  • 0: The Connector did not count the words in this content item.

Tip: To filter items by the values in the Page, Source, Target(s), Created On, or User columns, enter text in the text boxes at the top of the columns. The queue automatically displays only items that match the values in the text boxes.

  1. Optional. Select the check boxes of the items to send out for translation. The Connector will send out these items for translation as a single translation job. This step is required only if you do not want to send out all the items for translation.

Note about team profiles: If one or more paths are configured for your team profile, you can select only pages that are in these paths for translation. The path configuration does not restrict your selection of digital assets, tags, and dictionaries (i18n items).

  1. Below the list of content items, in the Translation Job tab, enter the following settings:

Setting Description
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:
  • Marketing
  • Technical
  • Legal
Note: You may see different content types if your company has configured custom content types.
Choose LSP If multiple translation providers are configured for your team profile, select the translation provider to whom you want to send this translation job. If you select Lionbridge Freeway, the following additional Freeway-specific fields are displayed:
Special Instruction Any additional instructions for Freeway, which are sent as metadata. Available only if the selected translation provider in the Choose LSP box, above, is the Lionbridge Freeway Type.
Analysis Code The Freeway analysis codes for the translation. Displayed only if:
  • In the Choose LSP box, above, the selected provider is the Lionbridge Freeway Type.
  • The Connector is configured to display these fields.

    You specify the analysis codes that are relevant to your content. Your Lionbridge setup determines which analysis codes are available for you to specify, and the values available for selection for each analysis code. For example, the Region, Department, and Priority analysis codes may be available for you to specify.
Translation Quote Select this check box to inform the translation provider that you want to receive a quote before the translation process starts.

Note: This check box is displayed only if the selected translation provider is configured to support providing a quote before the translation process starts.
Job Name Your name for this translation job. By default this includes the username, date, and time when you created the job, for example: Submit by [admin] @ 2016-12-20 6.57 PM. This is stored in the CQJobName attribute in the XML that the Connector sends to the translation provider.
PO Reference Enter the purchase order reference number.
Job Description Additional information about this job. This is stored in the CQJobDescription attribute in the XML that the Connector sends to the translation provider.
Notification Emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.
In-country Reviewer Optional. This is generally the name of the localization reviewer, which is stored in the InCountryReviewer attribute in the XML sent to the translation provider. By default, this field is hidden.
  1. Optional. Click the Reference Files tab to open it. You can send reference files (support assets) to your translation provider as part of a translation job. This provides helpful context for the translator.

For instructions on adding reference files in Adobe Experience Manager, refer to the Adobe Experience Manager documentation for uploading digital assets:

Note: This feature is available only if the Allow Reference Files for Translation Job check box is selected in the UI and Default Settings section of the Configuration page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

a. Click the down arrow and navigate to the reference file or folder containing reference files. b. Select the reference file or folder containing reference files and click Select. c. Repeat the previous steps for each reference file or folder containing reference files that you want to include.

The Connector will send all specified files and all files in the specified folders to the translation provider.

  1. Optional. Click the Overwrite options tab to open it. You can overwrite translation settings that were specified when the items were originally submitted to the Translation Queue. Some of the settings described below may not be available, depending on your company’s configuration.

a. In the Overwrite section, if you want to overwrite any translation settings for the items to send out for translation, select this check box. b. In the Overwrite section, select or clear the check boxes for the individual settings, as described below.

Translation Setting Description
Translate field 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.
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.
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.
  • If this column has a value of Yes, the Connector does not overwrite unique source content that already exists in the target pages.
  • If this column is blank, the Connector does overwrite unique source content that already exists in the target pages
Relevant only to page items.
Only translate content in locked components See the description of Translate Locked, above. Relevant only to page items.
Leave component unlock after putting back translated content See the description of Leave Unlock, above. Relevant only to page items.
Allow translate content from Not-Sync’d components See the description of Translate Not-Sync’d, above. Relevant only to page items.
Deadline The requested date for receiving the translated content back from the translation provider. Click in the field and select a date in the calendar that opens.
Use Local TM See the description of Use Local TM, above.
Notes Enter any additional information about this translation job. This information is sent to the translation provider as a comment in the metadata of the translation package.
  1. Send out the items to the translation provider from the Translation Job tab. If necessary, click that tab again to open it. Do one of the following:
    • To send all items in the Translation Queue to the translation provider, click Send out all pages for translation.
    • To send the selected items in the Translation Queue to the translation provider, click Send out checked pages for translation.

A message box opens, confirming that you want to send the files for translation.

  1. Click OK.

The Connector starts preparing to send the files for translation. The Job Details tab of the Translation Status page opens, where you can monitor the progress. For details, see Monitoring Pages in a Translation Job and Viewing Translated Content.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

6 - Preparing to Send Content for Translation from Adobe Experience Manager Translation Integration

Before you can send content for translation from the Adobe Experience Manager translation integration, you must specify the following configurations for the site to translate:

  • The translation integration configuration contains the Adobe Experience Manager settings for how to translate your content.
  • The Connector cloud configuration contains a set of Connector settings.

You must also create a translation project within Adobe Experience Manager.

To prepare the site for translation:
  1. In the Adobe Experience Manager rail, click Sites, and navigate to the site to translate.

  2. Select the site, and then select More > View Properties from the menu.

  3. In the top-left corner, click Edit.

  4. Click the Cloud Services tab.

  5. In the Translation Integration section, select the appropriate translation integration configuration for the Connector. These are the Adobe Experience Manager settings for how to translate your content. For more information, contact your system administrator or refer to “Creating a Translation Integration Configuration for the Connector” in the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

  6. In the Lionbridge section, select the appropriate Connector cloud configuration. Each configuration contains a set of Connector settings. For more information, contact your system administrator or refer to “Creating an Adobe Experience Manager Cloud Configuration for the Connector” and “Editing Connector Cloud Configuration Settings” in the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

Note: If the Lionbridge section does not exist, you can create it by clicking Add Configuration and then selecting Lionbridge from the list.

  1. Click Done.

  2. You create a translation project from Adobe Experience Manager’s Sites console. You can create a project either for a new language copy or to update an existing language copy. For detailed instructions, refer to “Creating Translation Projects Using the References Panel” in the Adobe Experience Manager documentation:

7 - Resending a Translation Job

You can send previously sent jobs for translation from the Status tab of the Translation Status page. You can modify the content items, source and target languages, translation provider, translation options, and job options before resending the job. You can also specify an LSP-specific configuration for the job to resend.

To resend a translation job:
  1. Do one of the following to open the Status tab of Translation Status page:

  • In the Touch-Optimized UI of Adobe Experience Manager, click the Tools icon and then click Lionbridge Connector in the Adobe Experience Manager rail. (This opens the Connector in a new browser tab.) Then, click Translation Status in the Lionbridge Connector rail.
  • In the Classic UI of Adobe Experience Manager, scroll down and click Lionbridge Connector in the right pane. Then, click Translation Status in the Lionbridge Connector rail.
  • In your Web browser, navigate to /content/ctctranslation/status.html on your Adobe Experience Manager instance.

For a detailed description of this page, see Monitoring Jobs.

  1. In the Job column, locate the translation job to resend, and click the Re-Send button .

The Content and Languages tab of the Re-send translation job dialog box opens.

This tab displays a list of all content items that were sent for translation in the previous job, including the corresponding source and target languages. By default, all content items are selected for inclusion in the new job.

  1. Optional. Clear the check box boxes of any content items to exclude from the new translation job.

  2. Optional. Click the Re-Select Languages tab to open it.

This tab enables you to change the source and target languages of the translation job.

a If you want to change the source and/or target languages of the job, select the Reset source and target languages check box. b Optional. If you want to change the source language of the content items to send out for translation, then in the Select source language dropdown list, select the new source language. c Optional. If you want to change the target languages into which the content items are translated, then in Translate into the following target languages section, select the check boxes of the new target languages.

  1. Optional. Click the LSP and Options tab to open it.

This tab displays the translation provider (LSP) and translation options from the previously sent job. Modify any of the following translation options:

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 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.
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. Optional. To change the translation provider (LSP), select it in the Choose LSP dropdown list. Depending on the translation provider you select, additional fields may be displayed. For example:
  • If you select the SDL TMS translation provider, then the TMS Config field is displayed. Select an SDL TMS configuration that was defined in the TMS GUID Config page. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide. In the second dropdown list, select your SDL TMS profile.
  • If you select the Lionbridge Freeway translation provider, the following additional fields are displayed:
Field Description
Special Instruction Any additional instructions for Freeway, which are sent as metadata. Available only if the selected translation provider in the Choose LSP box, above, is the Lionbridge Freeway Type.
Analysis Code The Freeway analysis codes for the translation. Displayed only if:

* In the **Choose LSP** box, above, the selected provider is the Lionbridge Freeway Type.
* The Connector is configured to display these fields.

You specify the analysis codes that are relevant to your content. Your Lionbridge setup determines which analysis codes are available for you to specify, and the values available for selection for each analysis code. For example, the Region, Department, and Priority analysis codes may be available for you to specify.
  1. Click the Translation Job tab to open it.

You use this tab to specify the following job settings:

Option Description
Job name Your name for this translation job. By default this is [Resend] and the name of the previously sent translation job. This is stored in the CQJobName attribute in the XML that the Connector sends to the translation provider.
Job description Additional information about this job. This is stored in the CQJobDescription attribute in the XML that the Connector sends to the translation provider.
PO Reference Enter the purchase order reference number.
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:

* Marketing
* Technical
* Legal

**Note:** You may see different content types if your company has configured custom content types.
Deadline The date you are requesting for the translated content to return. Click in the field and select a date in the calendar that opens. This information is sent to the translation provider as metadata of the translation package.

Recommendation: Discuss whether to use this feature with your translation provider(s).
Quote Select this check box to inform the translation provider that you want to receive a quote before the translation process starts.

Note: This check box is displayed only if the selected translation provider is configured to support providing a quote before the translation process starts.
Reference Files You can send reference files (support assets) to your translation provider as part of a translation job. This provides helpful context for the translator.

For instructions on adding reference files in Adobe Experience Manager, refer to the Adobe Experience Manager documentation for uploading digital assets:

* version 6.2: https://helpx.adobe.com/experience-manager/6-2/assets/using/managing-assets-touch-ui.html
* version 6.3: https://helpx.adobe.com/experience-manager/6-3/assets/using/managing-assets-touch-ui.html
* version 6.4: https://helpx.adobe.com/experience-manager/6-4/assets/using/managing-assets-touch-ui.html
* version 6.5: https://helpx.adobe.com/experience-manager/6-5/assets/using/managing-assets-touch-ui.html

**Note:** This feature is available only if the **Allow Reference Files for Translation Job** check box is selected in the **UI and Default Settings** section of the **Configuration** page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

##### To add a reference file to the Connector:

1. Click the down arrow and navigate to the reference file or folder containing reference files.
2. Select the reference file or folder containing reference files and click Select.
3. Repeat the previous steps for each reference file or folder containing reference files that you want to include.

The Connector will send all specified files and all files in the specified folders to the translation provider.
Translation Notes Enter any additional information about this translation job. This information is sent to the translation provider as a comment in the metadata of the translation package.
Notification Emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.
In-country Reviewer Optional. This is generally the name of the localization reviewer, which is stored in the InCountryReviewer attribute in the XML sent to the translation provider. By default, this field is hidden.
  1. Click Send.

The Connector submits the job.

8 - Sending Content for Translation from Adobe Experience Manager Translation Integration

When you use the Adobe Experience Manager Translation Integration feature, you send out the content for translation as a translation job from a translation project in Adobe Experience Manager’s Projects console.

  1. From the Adobe Experience Manager rail, click Projects.
  2. Click the translation project.
  3. On the project’s Translation Job tile, click the commands menu in the top-right corner, and then Start to start the translation job.

If the Connector cloud configuration for the translation project sends content to the Translation Queue, then after the content is in the queue, either:

  • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.
  • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

For more information, refer to “Starting a Translation Job” in the Adobe Experience Manager documentation:

Note: When sending out content for translation from Adobe Experience Manager’s translation integration feature, the Connector does not support Adobe Experience Manager’s Request Scope feature, which is described in the “Scoping a Translation Job” section of the Adobe Experience Manager documentation at the above link.

Note about canceling translation jobs from Adobe Experience Manager’s translation integration feature: If you cancel a job that you sent to the Translation Queue, then the Connector deletes it from the queue. If you cancel a job that you sent directly out for translation, then Adobe Experience Manager attempts to cancel the job. The job’s status changes to Cancel.

9 - Sending Pages for Translation from Adobe Experience Manager Sidekick

Note: This section is only applicable for the users who are using AEM on-premise version older than AEM 6.4.

If you are using the Adobe Experience Manager Classic UI, you can send individual pages of content for translation directly from the Adobe Experience Manager Sidekick.

Tip: This method is ideal for ad-hoc translations or for sending small amounts of content for translation.

Note: If one or more paths are configured for your team profile, you can send only pages that are in those paths for translation.

To sending pages for translation from Sidekick:
  1. Double-click a page to open it with Sidekick, which is a floating toolbar.

  2. In Sidekick, click the Page tab .

  3. In the Page tab, scroll down and click the Translate Content option. 

The Connector’s Sidekick translation request interface opens. One of four possible Sidekick user interfaces is displayed, depending on your company’s configuration: there are two single-page (simple) interfaces and two multiple-page (wizard) interfaces.

  1. Use the following table to determine which user interface is displayed for your company:
Submit button/Next button Multiple Check Boxes Are Displayed for Advanced Translation Options For detailed instructions, see…
Submit button no Sidekick - Simple UI
Submit button yes Sidekick - Simple UI with Options
Next button no Sidekick - Wizard
Next button yes Sidekick - Wizard with Options

9.1 - Sidekick - Simple UI

You use this interface to submit content to the Translation Queue only.

  1. Enter the following information about the translation options:
Option Description
Translation scope Determine the scope of the pages to send for translation. This is one of the following:

* **Current page:** The Connector sends the current page for translation.
* **All sub pages:** The Connector sends all the sub-pages for translation. It does not send the current page.
* **Current page and all sub pages:** The Connector sends the current page and all its sub-pages for translation.
Source language Select the source language to send for translation.
Target language(s) Select one or more target languages to send for translation. The list displays all the languages that are set up in Adobe Experience Manager for your team.
  1. Click Submit to send the content to the Translation Queue.

A message box opens, confirming that the page or pages have been added to the queue.

  1. Click OK to close the message box.

After the content is in the Translation Queue, either:

  • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.

  • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

9.2 - Sidekick - Simple UI with Options

Sidekick - Simple UI with Options

You use this interface to submit content to the Translation Queue only.

  1. Enter the following information about the translation options:
Option Description
Translation scope Determine the scope of the pages to send for translation. This is one of the following:

* **Current page:** The Connector sends the current page for translation.
* **All sub pages:** The Connector sends all the sub-pages for translation. It does not send the current page.
* **Current page and all sub pages:** The Connector sends the current page and all its sub-pages for translation.
Source language Select the source language to send for translation.
Target language(s) Select one or more target languages to send for translation. The list displays all the languages that are set up in Adobe Experience Manager for your team.
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.
Translate Locked Content 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.
Unlock When Done 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.
Translate Non-Sync’d Components on this page 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.
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: Your company’s Connector configuration determines the default settings of these last five options. For more information, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

  1. Click Submit to send the content to the Translation Queue.

A message box opens, confirming that the page or pages have been added to the queue.

  1. Click OK to close the message box.

After the content is in the Translation Queue, either:

  • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.

  • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

9.3 - Sidekick - Wizard

You use this interface to submit content to the Translation Queue or directly for translation.

Note: Depending on your user permissions or your company configuration, you may not be able to send out content directly for translation.

  1. Enter the following information about the translation options:
Option Description
Translation scope Determine the scope of the pages to send for translation. This is one of the following:

* **Current page:** The Connector sends the current page for translation.
* **All sub pages:** The Connector sends all the sub-pages for translation. It does not send the current page.
* **Current page and all sub pages:** The Connector sends the current page and all its sub-pages for translation.
Source language Select the source language to send for translation.
Target language(s) Select one or more target languages to send for translation. The list displays all the languages that are set up in Adobe Experience Manager for your team.
  1. Click Next.

The second page of the wizard opens.

The following options are available:

Option Description
Source language The source language you selected in the previous page of the wizard. Read-only. To change this value, click Back.
Target languages The target languages, including the number of target languages, you selected in the previous page of the wizard. Read-only. To change this value, click Back.
Deadline The requested translation deadline. This is the date when you expect the translated content to return. Click in the field and select a date in the calendar that opens. This information is sent to the translation provider as metadata of the translation package.

Recommendation: Discuss with your translation provider whether to use the information in this field.
Page Path/Status This list displays the path and the name of all pages you are sending for translation.
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.
Submit Translation Indicate where to submit the specified pages for translation. This is one of the following:

* **Add to queue:** The Connector adds the specified pages to the Translation Queue. After the content is in the Translation Queue, either:

* You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.
* Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

* **Send as a new job:** The Connector immediately sends out the specified pages for translation as a new translation job, according to your company’s routing rules and the options you specify below.

**Note:** This option is available only to users with permission to send pages directly out for translation.
Reference Files You can send reference files (support assets) to your translation provider as part of a translation job. This provides helpful context for the translator.

For instructions on adding reference files in Adobe Experience Manager, refer to the Adobe Experience Manager documentation for uploading digital assets:

* version 6.2: https://helpx.adobe.com/experience-manager/6-2/assets/using/managing-assets-touch-ui.html
* version 6.3: https://helpx.adobe.com/experience-manager/6-3/assets/using/managing-assets-touch-ui.html
* version 6.4: https://helpx.adobe.com/experience-manager/6-4/assets/using/managing-assets-touch-ui.html
* version 6.5: https://helpx.adobe.com/experience-manager/6-5/assets/using/managing-assets-touch-ui.html

**Note:** This feature is available only if the **Allow Reference Files for Translation Job** check box is selected in the **UI and Default Settings** section of the **Configuration** page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

##### To add a reference file to the Connector:

1. Click the Search icon and navigate to the reference file or folder containing reference files.
2. Select the reference file or folder and click **OK**.

The path you selected is displayed in the text box below.

1. Repeat the previous steps for each reference file or folder containing reference files that you want to send to Freeway.

The Connector will send all files in the specified paths to Freeway.

**Note:** Displayed only if you select Lionbridge Freeway as the translation provider (LSP) in the **Choose LSP** field below.
Job Name Your name for this translation job. This information is sent to your translation provider.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Job Description Your description for the translation job. This information is sent to your translation provider.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Notification Emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
In-country Reviewer Optional. This is generally the name of the localization reviewer, which is stored in the InCountryReviewer attribute in the XML sent to the translation provider. By default, this field is hidden.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:

* Marketing
* Technical
* Legal

**Note:** You may see different content types if your company has configured custom content types.

Required and relevant only when Send as a new job is selected in the **Submit Translation** field, above.
Choose LSP Select the translation provider for your translation job. Your Connector administrator specifies the default translation provider.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Special Instruction Any additional instructions for Freeway.

Note: Displayed only if the selected translation provider in the Choose LSP box, above, is the Lionbridge Freeway Type.
Freeway Analysis Codes The Freeway analysis codes for the translation. Displayed only if:

* In the Choose LSP box, above, the selected provider is the Lionbridge Freeway Type.
* The Connector is configured to display these fields.

You specify the analysis codes that are relevant to your content. Your Lionbridge setup determines which analysis codes are available for you to specify, and the values available for selection for each analysis code. For example, the Region, Department, and Priority analysis codes may be available for you to specify.
  1. Click Submit to submit the specified pages either to the Translation Queue or directly to translation, as you indicated above.
  2. If you submitted the pages directly for translation, a message box opens, confirming that you want to send out the translation job. Click OK to proceed.
  3. The wizard page displays a green box in the Status column, indicating that the translation submission was successful.
  4. Click Close to close the wizard.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

Tip: You can monitor the translation progress from within the Connector. For detailed instructions, see Monitoring Translation Status and Jobs and Viewing Translated Content.

9.4 - Sidekick - Wizard with Options

You use this interface to submit content to the Translation Queue or directly for translation.

Note: Depending on your user permissions or your company configuration, you may not be able to send out content directly for translation.

  1. Enter the following information about the translation options:
Option Description
Translation scope Determine the scope of the pages to send for translation. This is one of the following:

* **Current page:** The Connector sends the current page for translation.
* **All sub pages:** The Connector sends all the sub-pages for translation. It does not send the current page.
* **Current page and all sub pages:** The Connector sends the current page and all its sub-pages for translation.
Source language Select the source language to send for translation.
Target language(s) Select one or more target languages to send for translation. The list displays all the languages that are set up in Adobe Experience Manager for your team.
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.
Translate Locked Content 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.
Unlock When Done 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.
Translate Non-Sync’d Components on this page 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.
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: Your company’s Connector configuration determines the default settings of these last five options. For more information, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

  1. Click Next.

The second page) of the wizard opens.

The following options are available:

Option Description
Source language The source language you selected in the previous page of the wizard. Read-only. To change this value, click Back.
Target languages The target languages, including the number of target languages, you selected in the previous page of the wizard. Read-only. To change this value, click Back.
Deadline The requested translation deadline. This is the date when you expect the translated content to return. Click in the field and select a date in the calendar that opens. This information is sent to the translation provider as metadata of the translation package.

Recommendation: Discuss with your translation provider whether to use the information in this field.
Page Path/Status This list displays the path and the name of all pages you are sending for translation.
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.
Submit Translation Indicate where to submit the specified pages for translation. This is one of the following:

* **Add to queue:** The Connector adds the specified pages to the Translation Queue. After the content is in the Translation Queue, either:

* You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.
* Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

* **Send as a new job:** The Connector immediately sends out the specified pages for translation as a new translation job, according to your company’s routing rules and the options you specify below.

**Note:** This option is available only to users with permission to send pages directly out for translation.
Reference Files You can send reference files (support assets) to your translation provider as part of a translation job. This provides helpful context for the translator.

For instructions on adding reference files in Adobe Experience Manager, refer to the Adobe Experience Manager documentation for uploading digital assets:

* version 6.2: https://helpx.adobe.com/experience-manager/6-2/assets/using/managing-assets-touch-ui.html
* version 6.3: https://helpx.adobe.com/experience-manager/6-3/assets/using/managing-assets-touch-ui.html
* version 6.4: https://helpx.adobe.com/experience-manager/6-4/assets/using/managing-assets-touch-ui.html
* version 6.5: https://helpx.adobe.com/experience-manager/6-5/assets/using/managing-assets-touch-ui.html

**Note:** This feature is available only if the **Allow Reference Files for Translation Job** check box is selected in the **UI and Default Settings** section of the **Configuration** page. For detailed instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

##### To add a reference file to the Connector:

1. Click the Search icon and navigate to the reference file or folder containing reference files.
2. Select the reference file or folder and click **OK**.

The path you selected is displayed in the text box below.

1. Repeat the previous steps for each reference file or folder containing reference files that you want to send to Freeway.

The Connector will send all files in the specified paths to Freeway.

**Note:** Displayed only if you select Lionbridge Freeway as the translation provider (LSP) in the **Choose LSP** field below.
Job Name Your name for this translation job. This information is sent to your translation provider.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Job Description Your description for the translation job. This information is sent to your translation provider.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Notification Emails Enter one or more email addresses that will receive notification when the content leaves Adobe Experience Manager and when it returns to Adobe Experience Manager. Use a comma to separate multiple email addresses.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
In-country Reviewer Optional. This is generally the name of the localization reviewer, which is stored in the InCountryReviewer attribute in the XML sent to the translation provider. By default, this field is hidden.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Content Type You can tag the content in a translation job as a specific content type. Depending on your company’s configuration, the Content API Platform may send the content to a specific translation provider based on the content type. Select one of the following content types:

* Marketing
* Technical
* Legal

**Note:** You may see different content types if your company has configured custom content types.

Required and relevant only when Send as a new job is selected in the **Submit Translation** field, above.
Choose LSP Select the translation provider for your translation job. Your Connector administrator specifies the default translation provider.

Required and relevant only when Send as a new job is selected in the Submit Translation field, above.
Special Instruction Any additional instructions for Freeway.

Note: Displayed only if the selected translation provider in the Choose LSP box, above, is the Lionbridge Freeway Type.
Freeway Analysis Codes The Freeway analysis codes for the translation. Displayed only if:

* In the **Choose LSP** box, above, the selected provider is the Lionbridge Freeway Type.
* The Connector is configured to display these fields.

You specify the analysis codes that are relevant to your content. Your Lionbridge setup determines which analysis codes are available for you to specify, and the values available for selection for each analysis code. For example, the Region, Department, and Priority analysis codes may be available for you to specify.
  1. Click Submit to submit the specified pages either to the Translation Queue or directly to translation, as you indicated above.
  2. If you submitted the pages directly for translation, a message box opens, confirming that you want to send out the translation job. Click OK to proceed.
  3. The wizard page displays a green box in the Status column, indicating that the translation submission was successful.
  4. Click Close to close the wizard.

For information about the events that occur when the Connector sends out content for translation, see Sending Content for Translation.

Tip: You can monitor the translation progress from within the Connector. For detailed instructions, see Monitoring Translation Status and Jobs and Viewing Translated Content.

10 - Sending Content to the Translation Queue Using Workflow

Note: This section is not applicable for the the AEM Cloud Connector. You can send content to the Translation Queue using the Sample_CT_Workflow_Translation workflow. For detailed integration instructions, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

You can send content to the Translation Queue using workflow:

After the content is in the Translation Queue, either:

  • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.

  • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

10.1 - Sending Content to the Translation Queue Using Workflow from the Inbox

Note about team profiles: If one or more paths are configured for your team profile, you can select only pages that are in these paths for translation. The path configuration does not restrict your selection of digital assets, tags, and dictionaries (i18n items).

To send content to the Translation Queue while using workflow from the Inbox:
  1. Do one of the following to open the Inbox:
  • In the Touch-Optimized UI of Adobe Experience Manager, click Tools in the Adobe Experience Manager rail. Then, in the Tasks section, click Inbox.
  • In the Classic UI of Adobe Experience Manager, click Inbox.
  • In your Web browser, navigate to /inbox.html on your Adobe Experience Manager instance.

The Inbox opens and displays workflow items.

  1. Select a workflow item, right-click, and select Complete from the context menu. 

The Complete Work Item dialog box opens.

The Next Step is Add page translation.

  1. In the Target Languages section, select the check boxes for the target languages into which to translate the content. The list displays all the languages that are set up in Adobe Experience Manager for your team.

  2. Click the Collapse icon to hide the Target Languages section. Alternatively, you can scroll down in the dialog box.

The Translation Options section is displayed.

Notes: The default settings for these options are specified in the Translation Default Settings section in the Configuration page. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide. Depending on your company’s configuration, some of the options described below may not be available:

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.
Target pages have content in source language 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.
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.
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.
Allow translate 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.

* 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.
  1. Click the Collapse icon to hide the Translation options section. Alternatively, you can scroll down in the dialog box.

  2. Optional. In the Comments section, enter any additional information about this workflow step. This is stored in Adobe Experience Manager.

  3. Click OK to send the content to the Translation Queue.

Note: To save your changes without sending the content to the Translation Queue, click Skip. You can return later to send the content to the queue.

After the content is in the Translation Queue, either:

  • You must access the Translation Queue and approve the pages you want to send out for translation. For detailed instructions, see Submitting Content for Translation from the Translation Queue.

  • Your company has schedules that automatically send out translation jobs from the Translation Queue. For details, refer to the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.