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:
- Sending Content for Translation Using the Bulk Translation Wizard
- Sending Pages and Assets for Translation Using the Globalization Tool
- Sending Files to the Translation Queue When You Roll Out Files
- Sending Pages for Translation from the Touch-Optimized UI (Adobe Experience Manager version 6.3 and higher only)
- Sending Pages for Translation from the Adobe Experience Manager Sidekick
- Sending Content to the Translation Queue Using Workflow
- Resending a Translation Job
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).
- For an overview of this feature, see Using the Adobe Experience Manager Translation Integration Framework with the Connector.
- For instructions on preparing to send out content for translation from Adobe Experience Manager, see Preparing to Send Content for Translation from Adobe Experience Manager Translation Integration.
- For instructions on sending out content for translation from Adobe Experience Manager, see Sending Content for Translation from Adobe Experience Manager Translation Integration.