Skip to main content
KARTHIKAV1
Level 2
Feb 4, 2025 7:10 AM UTC

Translation picking wrong language code

 

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.

3 replies

Shiv_Prakash_Patel
Community Advisor
Shiv_Prakash_PatelCommunity Advisor
Community Advisor
Feb 4, 2025 11:49 AM UTC

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,

Translate
Shiv Prakash
    Manisha_Mirchandani
    Manisha_Mirchandani
    Level 2
    Mar 5, 2025 7:54 AM UTC

    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]). 

    Translate
    kautuk_sahni
    kautuk_sahni
    Level 9
    Feb 18, 2025 8:29 AM UTC

    @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!

    Translate
    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...