Internationalisation | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Nupur_Jain
Adobe Employee
Nupur_JainAdobe EmployeeAccepted solution
Adobe Employee
August 18, 2020

Hi @imadullakhan 

 

For AEM maintains string translation in the form of keys and values that is i18n keys. You should start with Adobe documentation on internalisation https://docs.adobe.com/content/help/en/experience-manager-65/developing/components/internationalization/i18n-dev.html.

 

I would also suggest to go through these to understand the whole solution better:

  1. https://docs.adobe.com/content/help/en/experience-manager-65/developing/components/internationalization/i18n-extract.html
  2. https://docs.adobe.com/content/help/en/experience-manager-65/developing/components/internationalization/i18n-translator.html
  3. https://docs.adobe.com/content/help/en/experience-manager-65/developing/components/internationalization/i18n.html

Hope it helps!

Thanks!

Nupur

    imadullakhan
    imadullakhanAuthor
    Level 3
    August 18, 2020
    Thank you @Nupur.
    Nikhil-Kumar
    Community Advisor
    Nikhil-KumarCommunity Advisor
    Community Advisor
    August 18, 2020

    @imadullakhan 

    As mentioned by @nupur_jain, try to go through the documentation on i18n.
    You can also go through some blogs where people have shown the process of implementing it in AEM.
    https://www.nextrow.com/adobe-experience-manager/usecase-il8n-converting-components-based-userpreference

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

    http://aemcases.blogspot.com/2018/05/internationalization-i18n-in-aem-using.html

      imadullakhan
      imadullakhanAuthor
      Level 3
      August 18, 2020
      Sure @nikhil-kumar Thank You!
      Terms & ConditionsAccessibility statement

      Loading footer...