Translation picking wrong language code | Community
Skip to main content
K
KARTHIKAV1
New Participant
February 4, 2025

Translation picking wrong language code

  • February 4, 2025
  • 2 replies
  • 644 views

 

When adding a page for translation with target language en_gb, the source path is automatically set with en-gb instead of en_gb and translated page is created under en-gb. It seems like AEM is picking the first matching language in Sites, instead of correctly identifying the actual language code.

 

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

2 replies

kautuk_sahni
kautuk_sahni
Employee
February 18, 2025

@karthikav1 Did you find the suggestion helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

Kautuk Sahni
Shiv_Prakash_Patel
Shiv_Prakash_Patel
New Participant
February 4, 2025

Hi @karthikav1 ,

If you are using AEM Translation Projects, verify the translation job setup to ensure that en_gb is being used instead of en-gb.
In some cases, manually setting the language root in the translation configuration may help.

Regards,

Shiv Prakash
    Manisha_Mirchandani
    Manisha_Mirchandani
    New Participant
    March 5, 2025

    Hi @shiv_prakash_patel,

     

    We are trying translate any page under en_gb it's getting translated under en-gb. "-" always have preference.

    Let's say i have taken any page under hierarchy /content/projectname/en to translate into target language English(en_gb), it's creating translated page under /content/projectname/en-gb hierarchy in place of en_gb.

     

    Any feasible solution for above use case.

    Note - we are selecting correct language code in translation project(advance tab - English[en_gb]). 

    Terms & ConditionsAccessibility statement

    Loading footer...