You are here: User Guides > Connector for Adobe Experience Manager > Getting Started with the Connector > Key Features > Multiple Ways to Send Content for Translation

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.
  • Send content immediately to the translation provider.
  • Send content via the Translation Queue, which enables you to group items together by project, priority, target language, and require additional approval. For details, see Submitting Content for Translation from the Translation 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.