AEM Translator to Manage Dictionaries replicate change | Community
Skip to main content
daf99
daf99
Level 2
July 14, 2020
Solved

AEM Translator to Manage Dictionaries replicate change

  • July 14, 2020
  • 2 replies
  • 1957 views

Hello everyone,

I have implemented in my AEM project the Translator to Manage Dictionaries.

I was thinking that i should able to edit a label and then replicate that change for all the others AEM instances, but i don't any option to do it in the Translator interface. Then i found the note that is in the image below.

This note means that if have several AEM instances and i want to update some label without make a deploy, i have to make the same update in each one of the AEM instances manually?
There is no option to replicate the update as it's possible to be done with content?

Thank you.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vanegi

Hi @daf99 ,

To add to this, we have an OOTB implementation that AEM provides to manage dictionaries. A console for managing the various translations of texts used in component UI. This console is available at http://<hostname>:<port-number>/libs/cq/i18n/translator.html. See https://docs.adobe.com/content/help/en/experience-manager-64/developing/components/internationalization/i18n-translator.html for more details.

 

With respect to the given use case, the i18 keys can be replicated to publisher in different ways as mentioned below.

·         Manually creating the i18 nodes in publisher

·         Creating the package from author and deploying it to publisher

·         Replicating the nodes through tree activation

Login to treeactivation.html - http://<<Host>>:<<Port>>/etc/replication/treeactivation.html

 

 

Thanks,

Vaishali

2 replies

Nupur_Jain
Adobe Employee
Nupur_JainAdobe Employee
Adobe Employee
July 14, 2020

Hi @daf99 

 

The note you specified basically means that the translation dictionary should be part of source code. As a best practice, we keep the translation in code base and they are installed as part of deployment. As mentioned in note, this process makes tracking of changes easy and maintainable.

 

The translation dictionary interface is mostly used when we need to make changes that are urgent and needed  prior to deployment.

 

Also, the translation dictionary can be replicated using tree activation feature and should work properly. You can also read https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-i18n-nodes-activate-only-modified-nodes/qaq-p/369120

 

Hope it helps!

Thanks,

Nupur

    daf99
    daf99Author
    Level 2
    July 14, 2020
    Thanks @nupur_jain, i will test the solution that you suggests.
    vanegi
    Adobe Employee
    vanegiAdobe EmployeeAccepted solution
    Adobe Employee
    July 14, 2020

    Hi @daf99 ,

    To add to this, we have an OOTB implementation that AEM provides to manage dictionaries. A console for managing the various translations of texts used in component UI. This console is available at http://<hostname>:<port-number>/libs/cq/i18n/translator.html. See https://docs.adobe.com/content/help/en/experience-manager-64/developing/components/internationalization/i18n-translator.html for more details.

     

    With respect to the given use case, the i18 keys can be replicated to publisher in different ways as mentioned below.

    ·         Manually creating the i18 nodes in publisher

    ·         Creating the package from author and deploying it to publisher

    ·         Replicating the nodes through tree activation

    Login to treeactivation.html - http://<<Host>>:<<Port>>/etc/replication/treeactivation.html

     

     

    Thanks,

    Vaishali

    Terms & ConditionsAccessibility statement

    Loading footer...