Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

How to translate data for custom components in AEM as a Cloud Service

Avatar

Level 5

I have been using AEM as a Cloud Service. In that I have created few custom components. Then, I have implemented the Language copy for my site. But the custom components which I have created, their data on frontend is not being translated. Is there a way through which I can achieve translation for custom components too?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hello @nikita24tailor 

 

regarding i18n

If its the i18n translation that you are looking for, then you might want to visit https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/internationaliza...

https://www.tothenew.com/blog/i18n-implementation-using-sightly/ 

 

Even if i18n dictionary is set up, we need to use the relevant APIs to inform AEM to use them. It can be in:

  • Java source files.
  • JSP scripts.
  • Javascript in client-side libraries or in page source.
  • JCR node property values used in dialogs and component configuration properties.
  • Sightly

 

regarding translation:

If you are looking for translation, then you would need to declare the new component/properties in Translation rules.

How these translation rules are configured might change for different translation vendors. A generic approach is https://experienceleague.adobe.com/docs/experience-manager-learn/sites/translation/translation-rules... .

Please check with the team, how translation rules are defined for your project.


Aanchal Sikka

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hello @nikita24tailor 

 

regarding i18n

If its the i18n translation that you are looking for, then you might want to visit https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/internationaliza...

https://www.tothenew.com/blog/i18n-implementation-using-sightly/ 

 

Even if i18n dictionary is set up, we need to use the relevant APIs to inform AEM to use them. It can be in:

  • Java source files.
  • JSP scripts.
  • Javascript in client-side libraries or in page source.
  • JCR node property values used in dialogs and component configuration properties.
  • Sightly

 

regarding translation:

If you are looking for translation, then you would need to declare the new component/properties in Translation rules.

How these translation rules are configured might change for different translation vendors. A generic approach is https://experienceleague.adobe.com/docs/experience-manager-learn/sites/translation/translation-rules... .

Please check with the team, how translation rules are defined for your project.


Aanchal Sikka