Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Multi language supports in AEM

Avatar

Level 4

According to the AEM Document , Translating Content for Multilingual Sites , AEM supports human and machine translation workflows. Those are 

  • Human translation - Content is sent to your translation provider such as Translations.com, Microsoft, Lingotek and translated by professional translators.
  • Machine translation - The machine translation service immediately translates your content.Then what is the connection in i18 with the above two. Can someone explain please.

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@JakeCham  there are two types of content, static and dynamic.

The dynamic content changes very frequently, generally the content author authors this content. we need to send this content for translation.

The static content will not change very frequently and managed by the developer, just an example for this is placeholder text which you see in the search textbox. we cannot send this for translation because it is part of our code. We need to handle this via Java API or JS API. example: i18n.get("Search");

Refer to this article for more information

https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/internationaliza...

 

Java and Javascript APIs enable you to internationalize strings in the following types of resources:

  • Java source files.
  • JSP scripts.
  • Javascript in client-side libraries or in page source.
  • JCR node property values used in dialogs and component configuration properties.

View solution in original post

0 Replies

Avatar

Correct answer by
Community Advisor

@JakeCham  there are two types of content, static and dynamic.

The dynamic content changes very frequently, generally the content author authors this content. we need to send this content for translation.

The static content will not change very frequently and managed by the developer, just an example for this is placeholder text which you see in the search textbox. we cannot send this for translation because it is part of our code. We need to handle this via Java API or JS API. example: i18n.get("Search");

Refer to this article for more information

https://experienceleague.adobe.com/docs/experience-manager-65/developing/components/internationaliza...

 

Java and Javascript APIs enable you to internationalize strings in the following types of resources:

  • Java source files.
  • JSP scripts.
  • Javascript in client-side libraries or in page source.
  • JCR node property values used in dialogs and component configuration properties.

Avatar

Community Advisor

Yes @JakeCham

In AEM we have tow type of translation available, as you mentioned below;

With machine translation we have some constraints like supports for comparatively less languages, translated text is comparatively not up to the mark etc.

So for good content it has been recommended that use the Second form(Human translation) that provides so much flexibility like what are the fields you wanted to send it for translation, because we can not sent a link for translation.

We have used transperfect, a third party paid service, for the human translation and I found if very use full in many aspects.

Hope this will help.

Umesh Thakur