Translation support for AEM Content Fragments translation-support-content-fragments

Learn how Content Fragments can be localized and translated with Adobe Experience Manager. Mixed-media assets associated with a Content Fragment are also eligible to be extracted and translated.

Let’s take a look at some of the translation - capabilities inside of AEM. For this demonstration, we’ll be translating - the Arctic Surfing page provided in the WKND site. This content is located in the - English section of the DAM. It’s important to have - language folders set up before attempting any translations. Expanding the side menu, we see that this page only - has one language copy, the original English version. Let’s create a French - translation for this page. To make a language copy, - we select our page, create and choose language copy.
We’ll choose which language or languages we want to translate to.
We could create the structure and it would just copy the page, but what we’re going to - do is create the structure as well as a new translation project. We’ll give this a name and - we’ll go ahead and hit create. From here, we can navigate - into our AEM projects. Here’s a folder that houses - all of the translation jobs and we can see our French translation. If we drill into the project, you can see there is one translation job, which means we’ve only sent a single site’s page for translation. We can see what content on - the page is being translated. In this case, we have five - assets, one content fragment, and no tags. Taking a deeper look - into our translation job, we can see that the first entry is our site’s content page. Drilling down into that, we can see what content was included in that content fragment. Just based on a single content fragment, the translation engine was - smart enough to figure out that we needed to bring over - these four assets as well. We could kick off the translation job from within the French project or we can head back to our - translation overview page and kick off multiple - translations at the same time.
Once the translation job has completed, we can see our page, our - French language copy, and we can open it up and - inspect the translation. We can see here that our content fragment has been translated to French using the Microsoft machine - language translation engine and all of our images have - also been brought over. These images will now appear - in the French language folder.
If we go back into our French - language folder, under assets, we can now see the French language copy for our content fragment - as well as the images. The metadata for images has also been translated into French.
Experience Manager gives users - the flexibility to choose whether or not images associated - with a content fragment are sent for translation. This can be configured in tools, general, translation configuration. If we edit the translation - rules for content DAM, we can see the default - rules under general. Inspecting the reference tab, you can see the references - for content fragments and images are set to be translated. Removing or editing these rules - gives users the flexibility of what content gets translated. - -

Content Fragment Translation Use Cases content-fragment-translation-use-cases

Content Fragments are a recognized content type that AEM extracts to be sent to an external translation service. Several use cases are supported out of the box:

  1. A Content Fragment can be selected directly in the Assets console for language copy and translation.
  2. Content Fragments referenced on a Sites page are copied to the appropriate language folder and extracted for translation when the Sites page is selected for language copy.
  3. Inline media assets embedded inside a content fragment are eligible to be extracted and translated.
  4. Asset collections associated with a content fragment are eligible to be extracted and translated.

Translation Rules Editor translation-rules-editor

Experience Manager translation behavior can be updated by using the Translation Rules Editor. To update the translation, navigate to Tools > General > Translation Configuration at http://localhost:4502/libs/cq/translation/translationrules/contexts.html.

Out of the box configurations reference Content Fragments at fragmentPath with a resource type of core/wcm/components/contentfragment/v1/contentfragment. All components that inherit from the v1/contentfragment are recognized by the default configuration.

Translation Rules Editor