Hebrew Language ISO code Issue

Forum|Forum|6 years ago
April 3, 2019
4 replies
7230 views

Hello everyone,

I have a problem with the Hebrew translation. I added the language "he" to /etc/languages. I also added the translations to the dictionary, but AEM is returning the default entries.

After a little more research, AEM is trying to find the translation for "iw" (the old iso code for the Hebrew language) instead of "he" (the new iso code for Hebrew). If you add "iw" to /etc/languages and then add the translation for iw language (using the translation tool /libs/cq/i18n/translator.html), it works fine. But I need it to add HE.

I'm using language masters pages. But i also tried adding jcr:language="he" to my page.

Any help with this?

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

Best answer by rwinkle

Unfortunately I think you will have to use iw in the dictionary, but can use he for your site structure. We had the same issue and had to add iw-il to /etc/languages and an iw_il node under /apps/wcm/core/resources/languages like so:

 <he_il
        jcr:primaryType="nt:unstructured"
        country="*"
        defaultCountry="he_il"
        language="Hebrew"/>
    <iw_il
            jcr:primaryType="nt:unstructured"
            country="*"
            defaultCountry="iw_il"
            language="Hebrew(iw-il)"/>

But the country site is under he-il.

rwinkleAccepted solution

Level 2

Unfortunately I think you will have to use iw in the dictionary, but can use he for your site structure. We had the same issue and had to add iw-il to /etc/languages and an iw_il node under /apps/wcm/core/resources/languages like so:

 <he_il
        jcr:primaryType="nt:unstructured"
        country="*"
        defaultCountry="he_il"
        language="Hebrew"/>
    <iw_il
            jcr:primaryType="nt:unstructured"
            country="*"
            defaultCountry="iw_il"
            language="Hebrew(iw-il)"/>

But the country site is under he-il.

VictorToledo_Author

Level 3

thanks for the reply!! do you know if it's a aem bug?

rwinkle

Level 2

I believe it's a limitation in Java 8 locales. If you look at this page it uses iw-il Java 8 Supported Locales