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

Return to the regular view of this page.

Key Features

The Lionbridge Connector for Adobe Experience Manager (Connector) has the following key features:

1 - Multiple Ways to Send Content for Translation

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

  • There are the following multiple ways to send pages out for translation:

    • Send multiple content items, including pages, tags, dictionaries (i18n items), Content Fragments, Experience Fragments, adaptive forms, and digital assets (such as JPG and PDF files) using the Bulk Translation wizard. You can filter to exclude content, and send out requests for translations of one target language at a time as a separate translation job with its own requested-by date. For details, see Sending Content for Translation Using the Bulk Translation Wizard.

    • In Adobe Experience Manager version 6.3 and higher, you can send pages to translation directly from the Touch-Optimized UI of Adobe Experience Manager using the Translate Content page. For details, see Sending Pages for Translation from the Touch-Optimized UI (Adobe Experience Manager version 6.3 and higher only).

    • Send multiple pages, Content Fragments, Experience Fragments, adaptive forms, and digital assets (such as JPG and PDF files) using the Globalization Tool. You can add pages from multiple site paths, and/or upload page paths stored in CSV or XLS files. You can filter these pages by publication date, on time, off time, activation state, and page template. For details, see Sending Pages and Assets for Translation Using the Globalization Tool.

    • If you roll out files, the Connector can automatically send them to the Translation Queue, using the default translation settings configured for your company. For details, see Sending Files to the Translation Queue When You Roll Out Files.

    • If you use Adobe Experience Manager’s Classic UI, you can send one or more pages for translation from the Adobe Experience Manager Sidekick. Depending on your company’s configuration, you can send pages only to the Translation Queue, or you can choose whether to send them to the queue or directly out for translation. Your company’s configuration also determines which translation settings you can edit from the Sidekick. For details, see Sending Pages for Translation from the Adobe Experience Manager Sidekick.

    • If you are using Adobe Experience Manager’s translation workflow feature to automatically create new pages in the language branches of your site, the Connector can automatically send these new pages to the Translation Queue. For details, see Sending Content to the Translation Queue Using Workflow.

    • 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. For details, see Resending a Translation Job.

Note: You can send digital assets, such as JPG and PDF files, for translation from the Bulk Translation wizard and the Globalization Tool.

  • Depending on your company’s Connector configuration, you may be able to send content out for translation either immediately or via a queue.

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.

2 - Optimizing Translation

The Optimize Translation feature helps you reduce translation costs, by reducing the quantity of content that Connector sends to translation providers. It sends only changed content fields out for translation. To do this, it checks each component in the source version of the page for any content changes, and it sends 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.

However, this feature needs Connector translation backup data, and it increases the Connector processing time before sending out the items for translation.

This feature can be configured for your company and separately for the Bulk Translation wizard. You can also specify it by selecting the Use Local TM check box when you send individual pages to the Translation Queue or when you send out pages out directly for translation.

3 - Selecting a Translation Provider

If your company has multiple translation providers, your company’s Connector setup may enable you to select which one to use when you send out items for translation.

This feature is available in all user interfaces where you send out content for translation.

4 - Using the Adobe Experience Manager Translation Integration Framework with the Connector

This section describes how to use Adobe Experience Manager’s translation integration feature with the Connector. For detailed information about this feature, refer to the Adobe Experience Manager documentation, “Translating Content for Multilingual Sites” which is available at:

Note: For information on integrating the Connector with this feature, refer to steps 1-3 in the Adobe documentation at the above link and “Integrating the Connector with the Adobe Experience Manager’s Translation Integration Framework” in the Lionbridge Connector for Adobe Experience Manager Installation and Configuration Guide.

The Connector integrates with Adobe Experience Manager’s translation integration framework feature. This feature enables you to create translation projects and start translation jobs from within Adobe Experience Manager. When you use this integration, you create translation projects and start translation jobs in Adobe Experience Manager, but otherwise you can manage the projects and jobs in the same way that you manage them for jobs that you send directly from the Connector. With this integration, you can:

  • use Connector’s comprehensive settings in translation jobs sent from Adobe Experience Manager

  • send translation jobs to the Translation Queue or directly to translation providers

  • monitor translation jobs from the Connector

  • view translated content from the Connector

  • perform post-translation tasks from the Connector

Important: When using the Connector with the Translation Integration Framework, the Connector’s component-mapping, team-profiles, and language-mapping features are not available.

When using Adobe Experience Manager’s translation integration framework feature to send out content for translation, you complete the following general steps:

  1. You create the root page of a language branch of the site to site to translate, which is called a language copy. For detailed instructions, refer to “Preparing Content for Translation” in the Adobe Experience Manager documentation at: http://docs.adobe.com/docs/en/aem/6-1/administer/sites/translation/tc-prep.html.

Note: In the Connector, this step happens automatically when you send out content for translation. Additional user action is not required.

  1. Specify the translation integration configuration and the Connector cloud configuration 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.

For detailed instructions, see Preparing to Send Content for Translation from Adobe Experience Manager Translation Integration.

  1. You create a translation project from Adobe Experience Manager’s Sites console. For detailed instructions, see Preparing to Send Content for Translation from Adobe Experience Manager Translation Integration.

  2. You send out the content for translation as a translation job from a translation project in Adobe Experience Manager’s Projects console. For detailed instructions, see Sending Content for Translation from Adobe Experience Manager Translation Integration.

  3. You can monitor the progress of translation jobs started in Adobe Experience Manager’s translation integration feature. For detailed instructions, see Monitoring Translation Jobs Created in the Adobe Experience Manager Translation Integration.

  4. You can view translated content of translation jobs started in Adobe Experience Manager’s translation integration feature. For details, see Viewing Translated Content from Jobs Started in the Adobe Experience Manager Translation Integration.