Back to top image

Translate Content into a Custom Language with AEM Cloud

Adobe Experience Manager is flexible and can be configured for any language. AEM understands all ISO language codes, both 2 letter locales (en, fr, de) as well as 5 letter locales (en-US, fr-FR, de-DE).

List of default languages can be found in:

  • CRXDE by navigating to /libs/wcm/core/resources/languages
    languages.png
  • Or if you create a Translation Project.
    trans_project_prop.png

There are two steps for adding your custom language:

  1. Add Custom Language to AEM
  2. Configure language mapping for Smartling AEM Cloud Connector

Add Custom Language to AEM

  1. Open up CRXDE (http://localhost:4502/crx/de/index.jsp) and then browse to /libs/wcm/core/resources/languages
  2. You will see the list of languages that you see in the Translation Project. The language list is sorted by language code and not the language name.
  3. Open Package Manager
  4. Create a package contained filter for the node /libs/wcm/core/resources/languages 
  5.  Build and download the package
  6. Extract package content to `ui.apps` module of your AEM customization project
  7. Add filter for the new content
  8. Update `ui.apps`’s structure module
  9. Move languages node from `/libs` to `/apps`
  10. Add a language to `languages` content in format (example)

<zh_tw

        jcr:primaryType="nt:unstructured"

        country="Taiwan region"

        language="Chinese (Traditional)"/>

So, language list will be overlayed and deployed with your AEM customization project as a part of `apps.ui`

Configure Language Mapping for Smartling AEM Cloud Connector

Before you start to use the new custom language with the Smartling AEM Cloud Connector, you should set the proper language mapping (which locale in Smartling should be used for this language).

  1. Open CRXDE (http://localhost:4502/crx/de/index.jsp) and then browse to /apps/granite/translation/connector/config/smartling/languageMapping
  1. Open Package Manager
  2. Create a package contained filter for /apps/granite/translation/connector/config/smartling/languageMapping
  3. Build and download the package
  4. Extract package content into your `ui.apps` module of AEM customization project
  5. Add filter for new content
  6. Update `ui.apps`’s structure module
  7. Add a mapping for the new language in format

        <zh_tw

                jcr:primaryType="nt:unstructured"

                languageMapping="zh-TW"/>

 

Language mappings will be a part of the `ui.apps` module and will be deployed to AEM Cloud with your AEM customization project altogether. 

Table of Contents