Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
We have a website with multiple regions and languages, in the example I provide it's the Mexico/Spanish tree, e.g. /content/mysite/mx/es.
We have set up i18n keys for EN and ES locales.
Steps taken + Issues
No jcr:language provided in mx/es page, i18n translations rendered fine from ES
Switching jcr:language in mx/es page to es-mx, i18n translations rendered fine from ES
Removed an i18n translation value from the ES i18n dictionary
expected: EN translation picked up, as per org.apache.sling.i18n.impl.JcrResourceBundleProvider config
actual: nothing rendered
Re-added the missing ES i18n value, i18n translation rendered fine again
Added an i18n translation for MX-ES dictionary, i18n translation picked up properly (as mx/es page has mx-es locale set at this point). All the rest of the i18n translations are picked up from the ES i18n values
Removed the i18n translation from MX-ES dictionary
expected: ES translation is picked up
actual: nothing rendered
It was my assumption that the fallback mechanism in general is
Exact locale (e.g. MX-ES)
Closest locale (e.g. ES)
Default fallback (e.g. EN)
However this does not seem to work. Any clues or workarounds on that?
Thank you in advance.
Topics
Topics help categorize Community content and increase your ability to discover relevant content.