Esta conversación ha sido bloqueada debido a la inactividad. Cree una nueva publicación.
Nivel 1
Nivel 2
Iniciar sesión en la comunidad
Iniciar sesión para ver todas las insignias
Esta conversación ha sido bloqueada debido a la inactividad. Cree una nueva publicación.
Vistas
Respuestas
Total de me gusta
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/internationalizat....
I would also suggest to go through these to understand the whole solution better:
Hope it helps!
Thanks!
Nupur
Vistas
Respuestas
Total de me gusta
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/internationalizat....
I would also suggest to go through these to understand the whole solution better:
Hope it helps!
Thanks!
Nupur
Vistas
Respuestas
Total de me gusta
Vistas
Respuestas
Total de me gusta
@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-userprefer...
https://www.tothenew.com/blog/i18n-implementation-using-sightly/
http://aemcases.blogspot.com/2018/05/internationalization-i18n-in-aem-using.html
Vistas
Respuestas
Total de me gusta
Vistas
Respuestas
Total de me gusta