Getting language from other place rather than jcr:language page property | Community
Skip to main content
omrojas_lmn
February 7, 2018

Getting language from other place rather than jcr:language page property

  • February 7, 2018
  • 2 replies
  • 2433 views

We know that when the {'key' @ 'i18n'} is used, the engine looks for the message key in the i18n with the language defined in the jcr:language property in the page(or its parents). Is there a way, system-wise, to "override" the source of the language(or country), from the default location(jcr:language), to another property, without changing each and everyone of the @ i18n tags in the HTMLs?

Thank you!

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

2 replies

smacdonald2008
Level 10
February 7, 2018

Checking with our internal team on this.

smacdonald2008
Level 10
February 7, 2018

Team Replied:

"They need to clarify if this is about UI translation (i18n, AEM dictionary), or content translation.

For content translation, AEM primarily looks for languages in the path, e.g. www.site.com/en/content, www.site.cm/fr/content, etc, assuming an ISO language code is used. The jcr:language property has so far not been used for URL resolution. Beginning AEM 6.4 AEM will use the property, as a secondary resource for language resolution, in case the path does not contain an ISO language code. This will allow customers assigning arbitrary names to language copy roots, rather than ISO language codes.

"

smacdonald2008
Level 10
February 7, 2018

Also - for those reading this and want to know more about AEM and Translation -- see:

https://docs.adobe.com/ddc/en/gems/AEM-6-3-Ready-for-the-World---Translation-Integration-and-Best-Practices.html

Level 2
August 2, 2024

@omrojas_lmn  Were you able to achieve this feature ? I have a similar requirement.