Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

MSM with Translation framework

Avatar

Level 2

Hello, I have a hopefully fairly simple question.

 

Does MSM work with the native AEM translation framework?

In other words, would a translation connector that follows the structure outlined by the bootstrap conenctor be able to correctly operate on content of an AEM instance that employs MSM?

 

It seems to me that the answer is yes, however some of the phrasing here and here is causing doubts.

 

Thanks and kind regards,

Jan Humpál

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @JanHumpal 

 

Using bootstrap conenctor, One can integrate with human and machine translators to create language copies in AEM.

When you create a language copy in AEM, it asks for pages/assets that need to be translated and after selecting it, AEM translation Management process the source content and translates the content using the translation provider selected during translation. It creates a similar structure in AEM.

 

Suppose if you want to translate whole sites of we.retail Canada English whose path is /content/we-retail/ca/en to the German Language(de) then the target structure of translated copies will be /content/we-retail/ca/de

 

However, language copies never create a live copy relationship [Don't get confused with live copy concept]

The difference is explained very well in this thread https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/language-copy-vs-live-copy...

 

Regards,

Arpit

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

Hi @JanHumpal 

 

Using bootstrap conenctor, One can integrate with human and machine translators to create language copies in AEM.

When you create a language copy in AEM, it asks for pages/assets that need to be translated and after selecting it, AEM translation Management process the source content and translates the content using the translation provider selected during translation. It creates a similar structure in AEM.

 

Suppose if you want to translate whole sites of we.retail Canada English whose path is /content/we-retail/ca/en to the German Language(de) then the target structure of translated copies will be /content/we-retail/ca/de

 

However, language copies never create a live copy relationship [Don't get confused with live copy concept]

The difference is explained very well in this thread https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/language-copy-vs-live-copy...

 

Regards,

Arpit

Avatar

Level 2

Hello Arpit,

 

Thanks for the answer! I think I have a better idea of the whole concept now.

 

Just to confirm, this means that following recommended practices, both the translation framework and MSM actually operate independently.

Meaning that the translation framework creates language copies, which can then be utilized for different regions via Live copies?

 

So the answer to my original questions would be no and yes respectively? (With the caveat that those are actually two different questions despite what I had believed at the time of posting)

Avatar

Level 4

Hi Arpit, I am trying to use implement custom connector for AEM using the bootstrap implementation mentioned here https://github.com/Adobe-Marketing-Cloud/aem-translation-framework-bootstrap-connector

 

But I am getting the bundles in resolved state. Is there any other reference implementation available. I am using AEM 6.5.