2

Somewhat related to "What determines Source/Target Translation context in Experience Manager?" I wanted to confirm how Translation Manager works in Experience Manager when choosing a Component or Page.

We can click in the border for a Component or Page in XPM to start a translation job.

To be sure, does the Translate components option include just the Component Presentations on the Tridion Page as it exists in the Content Manager and not what's visible in delivery on the Staging page?

3

As what is different on staging via Experience Manager lives entirely in the preview database on the content delivery environment it would be impossible for Translation Manager to somehow find this content and queue it for translation; Translation Manager can only work with content that is present in the CM database as it is a pure-CM side extension.

| improve this answer | |
  • 1
    XPM could pass the list of Components to Translation Manager. But I don't think it does that. So: improbable yes, impossible... not really. :-) – Frank van Puffelen Dec 3 '14 at 19:07
  • 1
    This is one of the items on a list we have. Some people refer to this list as "the backlog". :) – Lars Møllebjerg Dec 3 '14 at 20:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.