Configuring the Translation Integration Framework
- Topics:
- Language Copy
CREATED FOR:
- Admin
The Translation Integration Framework integrates with third-party translation services to orchestrate the translation of AEM content.
- Connect to your translation service provider.
- Create a Translation Integration Framework configuration.
- Associate the cloud configurations with your pages.
For an overview of the content translation features in AEM, see Translating Content for Multilingual Sites.
Connecting to a Translation Service Provider
Create a cloud configuration that connects AEM to your translation service provider. AEM includes the capability to connect to Microsoft Translator by default.
The following translation vendors provide an implementation of the new API for the Translation Projects. Links to learn more about the integration:
- Translations.com (Adobe Exchange Premier Partner)
- Clay Tablet Technologies
- Lionbridge
- Memsource
- Cloudwords
- XTM Cloud
- Lingotek
- Smartling
- SDL
- Systran
- Altlang
- Microsoft (Microsoft Translator is pre-installed in AEM)
After you install a connector package, you can create a cloud configuration for the connector. Typically, you need to provide your credentials for authenticating with the translation service. For information about adding a cloud configuration for the Microsoft Translator connector, see Integrating with Microsoft Translator.
You can create multiple cloud configurations for the same connector if required. For example, create one configuration for each of the accounts or projects that you have with the same vendor.
After you configure a connection, you can create the translation integration framework configuration that uses it.
Creating a Translation Integration Configuration
Create a translation integration framework configuration to specify how to translate your content. The configuration includes the following information:
- Which translation service provider to use.
- Whether human or machine translation is to be performed.
- Whether to translate other content that is associated with a page or asset, such as tags.
After you create a framework configuration, you associate the cloud configuration with the pages that you want to translate according to the configuration. When the translation process is started, the translation workflow proceeds according to the associated framework configuration.
When different sections of your website have different translation requirements, create multiple framework configurations accordingly. For example, a multilingual website includes English, Spanish, and Japanese language copies. The site owner uses two different translation service providers for Spanish and Japanese translations. Therefore, two configurations of the framework are configured. Each configuration uses a different translation service provider.
After you configure a translation integration framework, you can associate it with the pages that use it.
Note: For an overview of the content translation features in AEM, see Translating Content for Multilingual Sites.
A single configuration of the framework controls how to translate page content, community content, and assets.
Sites Configuration Properties
The Sites properties control how the translation of page content is performed.
Property | Description |
---|---|
Translation Workflow |
Select the translation method that the framework performs for site content:
|
Translation Provider | Select the translation provider to perform the translation. A provider appears in the list when their corresponding connector is installed. |
Content Category | (Machine Translation Only) A category that describes the content that you are translating. The category can affect the choice of terminology and phrasing when translating content. |
Translate Tags | Select to translate tags that are associated with the page. |
Translate Page Assets |
Select how to translate assets that are added to components from the file system or referenced from Assets:
|
Auto-Execute Translation | Select to execute translation jobs automatically after translation projects are created. You do not have an opportunity to review and scope the translation job when you select this option. |
Communities Configuration Properties
Communities properties control how the translation of user-generated content is performed. The translation of user-generated content always uses machine translation. For more information, see Translating User Generated Content.
Property | Description |
---|---|
Translation Provider | Select the translation provider to perform the translation. The provider for which cloud configurations are created appear in the list. |
Content Category | A category that describes the content that you are translating. The category can affect the choice of terminology and phrasing when translating content. |
Choose A Locale To Use As The Global Share Store | (Optional) By selecting a locale for storing UGC, posts from all language copies will appear in one global conversation. By convention, choose the locale for the base language for the website. Choosing No Common Store will disable global translation. By default, global translation is disabled. |
Assets Configuration Properties
Assets properties control how to configure assets. For more information about translating assets, see Creating Language Copies for Assets.
Property | Description |
---|---|
Translation Workflow |
Select the type of translation that the framework performs for assets:
|
Translation Provider | Select the translation provider to perform the translation. A provider appears in the list when their corresponding connector is installed. |
Content Category | (Machine Translation only) A category that describes the content that you are translating. The category can affect the choice of terminology and phrasing when translating content. |
Translate Assets | Select to include assets in the translation project. |
Translate Metadata | Select to translate asset metadata. |
Translate Tags | Select to translate tags that are associated with the asset. |
Auto-Execute Translation | Select to execute translation jobs automatically after translation projects are created. You do not have an opportunity to review or scope the translation job when you select this option. |
-
In the side bar, click or tap Tools > Operations > Cloud > Cloud Services.
-
In the Translation Integration area, whether any configurations have been created determines which link appears:
- If no configurations have been created, click or tap Configure Now.
- If configurations already exist, click or tap Show Configurations, and then click or tap the + link that appears next to Available Configurations.
-
Type a name for the configuration and then click or tap Create.
-
Configure the properties on the Sites, Communities, and Assets tab, and then click or tap OK.
Configuring Pages for Translation
To configure the translation of your source pages into other languages, associate the pages with the following cloud configurations:
- The cloud configuration that connects AEM to your translation provider.
- The translation integration framework that configures the details of the translation.
Note that the translation integration framework cloud configuration identifies the cloud configuration to use for connecting to the service provider. When you associate a source page with a framework cloud configuration, the page must be associated with the service provider cloud configuration that the framework cloud configuration uses.
When you associate a page with a cloud configuration, the descendants of the page inherit the association. For example, if you associate the /content/geometrixx/en/products page with a Translation Integration Framework, the Products page and all pages below it are translated according to the framework.
When required, you can override the association on a descendent page. For example, the content of a web site is mostly about clothing. However, one branch of pages describes the company. The root page of the site is associated with a Translation Integration Framework that specifies machine translation using the Clothing category. The branch that describes the company uses a framework that performs machine translation using the General category.
Further, for any communities SCF components on the pages, the user generated content (UGC) will include the ability for users to translate content. For more information, see Translation of User Generated Content.
Associating a Page with a Translation Provider
Associate a page with the translation provider that you are using to translate the page and descendent pages.
- In the Sites console, select the page to configure and click or tap View Properties.
- Click or tap Edit then click or tap the Cloud Services tab.
- Click or tap Add Configuration > Translation Integration.
- Select the translation provider to use, and then click or tap Done.
Associating Pages with a Translation Integration Framework
Associate a page with the Translation Integration Framework that defines how you want to perform the translation of the page and descendent pages.
- In the Sites console, select the page to configure and click or tap View Properties.
- Click or tap Edit then click or tap the Cloud Services tab.
- Click or tap Add Configuration > Translation Integration.
- Select the translation integration framework to use, and then click or tap Done.
More help on this topic
Experience Manager
- Administering User Guide overview
- Sites Features
- Website Administration
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Configure the Rich Text Editor
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- Configuring RTE for Producing Accessible Sites
- The Link Checker
- Troubleshooting AEM
- Audit Log Maintenance in AEM 6
- Editor
- Managing Access to Workflows
- Using cURL with AEM
- Configuring Undo for Page Editing
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Administering Workflows
- Configuring Search Forms
- Tools Consoles
- Reporting
- Administering Workflow Instances
- Configuring Layout Container and Layout Mode
- Enabling Access to Classic UI
- Starting Workflows
- Configure the Rich Text Editor plug-ins
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Content Disposition Filter
- Personalization
- eCommerce
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Creative Cloud
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Best Practices for Email Templates
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Adobe Classifications
- Solutions Integration
- Target Integration with Experience Fragments
- Best Practices
- Content Management