Creating Translation Projects for Content Fragments
In addition to assets, Adobe Experience Manager (AEM) Assets supports language copy workflows for content fragments (including variations). No additional optimization is required to run language copy workflows on content fragments. In each workflow, the entire content fragment is sent for translation.
The types of workflows that you can run on content fragments is exactly similar to the workflow types you run for assets. Also, the options available within each workflow type match the options available under the corresponding workflows types for assets.
You can run the following types of language copy workflows on content fragments:
Create and translate
In this workflow, content fragments to be translated are copied to the language root of the language to which you want to translate. In addition, depending upon the options you choose, a translation project is created for the content fragments in the Projects console. Depending on the settings, the translation project can be started manually or allowed to run automatically as soon as the translation project is created.
Update language copies
When the source content fragment is updated or modified, the corresponding locale/language specific content fragment requires retranslation. The update language copies workflow translates an additional group of content fragments and includes it in a lanugage copy for a particular locale. In this case, the translated content fragments are added to the target folder that already contains previously-translated content fragments.
Create and translate workflow
The Create and translate workflow includes the following options. The procedural steps associated with each option are similar to those associated with the corresponding option for assets.
Update language copies workflow
The Update language copies workflow includes the following options. The procedural steps associated with each option are similar to those associated with the corresponding option for assets.
- Create a new translation project: For procedure steps, see Create a new translation project for assets (update workflow).
- Add to existing translation project: For procedure steps, see Add to existing translation project for assets (update workflow).
You can also create temporary language copies for fragments similar to the way you create temporary copies for assets. For details, see Creating temporary language copies for assets .
Translating mixed media fragments
AEM lets you translate content fragments that include various types of media assets and collections. If you translate a content fragment that includes inline assets, the translated copies of these assets are stored under the target language root.
If the content fragment includes a collection, the assets within the collection are translated along with the content fragment. The translated copies of the assets are stored within the appropriate target language root at a location that matches the physical location of the source assets under the source language root.
To be able to translate content fragments that include mixed media, first edit the default translation framework to enable the translation of inline assets and collections associated with content fragments.
- Click/tap the AEM logo, and navigate to Tools > Deployment > Cloud Services .
- Locate Translation Integration under Adobe Marketing Cloud , and click/tap Show Configurations .
- From the list of available configurations, click/tap Default configuration (Translation Integration configuration) to open the Default configuration page.
- Click Edit from the toolbar to display the Translation Config dialog.
- Navigate to the Assets tab, and choose Inline Media Assets and Associated Collections from the Translate Content Fragment Assets list. Click/tap OK to save the changes.
- From within the English root folder, open a content fragment.
- Click/tap the Insert Asset icon.
- Insert an asset into the content fragment.
- Click/tap the Associate Content icon.
- Click/tap Associate Content .
- Select a collection and include it into the content fragment. Click/tap Save .
- Select the content fragment, and click/tap the GlobalNav icon.
- Select References from the menu to display the References pane.
- Click/tap Language Copies under Copies to display the language copies.
- Click/tap Create & Translate from at the bottom of the panel to display the Create & Translate dialog.
- Select the target language from the Target Languages list.
- Select the translation project type from the Project list.
- Specify the title of the project in the Project Title box and then click/tap Create .
- Navigate to the Projects console, and open the project folder for the translation project you created.
- Click/tap the project tile to open the project details page.
- From the Translation Job tile, verify the number of assets to be translated.
- From the Translation Job tile, start the translation job.
- Click the ellipses at the bottom of the Translation Job tile to display the status of the translation job.
- Click/tap the content fragment to check the path of the translated associated assets.
- Review the language copy for the collection in the Collections console.Notice that only the content of the collection are translated. The collection itself is not translated.
- Navigate to the path of the translated associated asset. Observe that the translated asset is stored under the target language root.
- Navigate to the assets within the collection that are translated along with the content fragment. Observe that the translated copies of the assets are stored at the appropriate target language root.The procedures for adding a content fragment to an existing project or to perform update workflows are similar to the corresponding procedures for assets. For guidance on these procedures, refer to the procedures described for assets.