Expand my Community achievements bar.

SOLVED

LocalizationUtils.getLocalizationRoot Unexpected Response

Avatar

Level 1

Hi everyone,

I’m encountering an issue with the LocalizationUtils.getLocalizationRoot method in AEM. When I call this method on a page, I get an unexpected result.

Example:

  • Page Path: /content/my-site/uk/en/my-page
  • Expected Result: /content/my-site/uk/en
  • Actual Result: /content/my-site/uk

I suspect this discrepancy is because “uk” is being interpreted as the language code for Ukrainian, whereas in my case, it represents the United Kingdom (UK).

Question: Is this behavior a bug, or is there a configuration I might be missing to correctly interpret “uk” as the United Kingdom?

Thanks in advance for your help!

1 Accepted Solution

Avatar

Correct answer by
Employee

Could you rename the 'uk' folder to 'en_GB' to align with the correct locale naming convention? The 'uk' code refers to Ukrainian, while 'en_GB' is the proper code for the United Kingdom.

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

Could you rename the 'uk' folder to 'en_GB' to align with the correct locale naming convention? The 'uk' code refers to Ukrainian, while 'en_GB' is the proper code for the United Kingdom.

Avatar

Level 1

Yes, I can do this. Is there any technical documentation or list of the standards, and / or list of countries and languages that AEM supports? Or is there source code that I can look at for this?