AEM Dictionary Translator

AEM TouchUI tool to translate labels for i18n internationalisation in AEM as a Cloud Service. The AEM Dictionary Translator is a replacement for the ClassicUI translator which is not available on AEMaaCS.

The AEM Dictionary Translator is available under Tools > Translation > Dictionary.

Installation

To deploy the AEM Dictionary Translator as an embedded package you need to update your pom.xml

1. Add the aem-dictionary-translator.all to the <dependencies> section

   <dependency>
     <groupId>be.orbinson.aem</groupId>
     <artifactId>aem-dictionary-translator.all</artifactId>
     <version><replace with last release version></version>
     <type>zip</type>
   </dependency>

2. Embed the package in with the filevault-package-maven-plugin in the <embeddeds> section

   <embedded>
      <groupId>be.orbinson.aem</groupId>
      <artifactId>aem-dictionary-translator.all</artifactId>
      <target>/apps/vendor-packages/content/install</target>
   </embedded>

3. Currently, AEMaaCS doesn't allow loading of i18n dictionaries outside /apps, /libs, /content/forms/af and /content/dam/formsanddocuments.

To mitigate this, update the org.apache.sling.i18n.impl.JcrResourceBundleProvider OSGi config to allow dictionaries in other folders, for example by using /content/dictionaries for all your editable dictionaries.

Example org.apache.sling.i18n.impl.JcrResourceBundleProvider OSGi config:

{
  "included.paths": [
    "/libs",
    "/apps",
    "/content/forms/af",
    "/content/dam/formsanddocuments",
    "/content/dictionaries"
  ]
}

Development

To build all the modules run in the project root directory the following command

mvn clean install

To build all the modules and deploy the all package to a local instance of AEM, run in the project root directory the following command

mvn clean install -PautoInstallSinglePackage

This project follows the AEM Archetype conventions so for further guidelines consult the available documentation.