internationalization(i18n) | Community
Skip to main content
July 1, 2021
Solved

internationalization(i18n)

  • July 1, 2021
  • 1 reply
  • 1133 views

Can we have  i18n in the conf folder in the cloud? If not how to have i18n in the cloud . because there is a concept of mutable and immutable objects.

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 BimmiSo

Hi @yashu99,

 

We can't have i18n in /conf. We need to keep it under apps. 

its a constraint of AEM as cloud that i18n dictionary translation - Does not work at runtime.

 Please check for more features and constraints 

https://www.linkedin.com/pulse/aem-cloud-service-glance-vivekanand-mishra/

 

Mutable vs. Immutable Areas of the Repository
/apps and /libs are considered immutable areas of AEM as they cannot be changed (create, update, delete) after AEM starts (i.e. at runtime). Any attempt to change an immutable area at runtime will fail.

Everything else in the repository, /content, /conf, /var, /etc, /oak:index, /system, /tmp, etc. are all mutable areas, meaning they can be changed at runtime.

 

Hope this helps

 

Thanks 

1 reply

BimmiSoAdobe EmployeeAccepted solution
Adobe Employee
July 1, 2021

Hi @yashu99,

 

We can't have i18n in /conf. We need to keep it under apps. 

its a constraint of AEM as cloud that i18n dictionary translation - Does not work at runtime.

 Please check for more features and constraints 

https://www.linkedin.com/pulse/aem-cloud-service-glance-vivekanand-mishra/

 

Mutable vs. Immutable Areas of the Repository
/apps and /libs are considered immutable areas of AEM as they cannot be changed (create, update, delete) after AEM starts (i.e. at runtime). Any attempt to change an immutable area at runtime will fail.

Everything else in the repository, /content, /conf, /var, /etc, /oak:index, /system, /tmp, etc. are all mutable areas, meaning they can be changed at runtime.

 

Hope this helps

 

Thanks 

July 1, 2021
Thanks Bimmi