Skip to main content
viveksachdeva
Community Advisor
viveksachdevaCommunity Advisor
Community Advisor
Oct 16, 2015 2:27 AM UTC
Solved

Issue with Machine Translation

I have developed a connector or machine translation that does not support storing translation in memory. Everytime I send a page for translation, it sends its parent pages also for translation. 

If my parent pages are already translated, it is an overhead in terms of cost. Is there a way to turn it off, some configuration maybe?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Sham_HC
Sham_HCAccepted solution
Level 10
Oct 16, 2015 2:27 AM UTC

in that case need to develop an custom workflow process. 

View in thread

4 replies

viveksachdeva
Community Advisor
viveksachdevaCommunity AdvisorAuthor
Community Advisor
Oct 16, 2015 2:27 AM UTC

Yah, I was thinking of it as last resort as creating a custom process step would mean copying all code from OOTB process and removing just the tranverseParent part...

Translate
Sham_HC
Sham_HCAccepted solution
Level 10
Oct 16, 2015 2:27 AM UTC

in that case need to develop an custom workflow process. 

Translate
viveksachdeva
Community Advisor
viveksachdevaCommunity AdvisorAuthor
Community Advisor
Oct 16, 2015 2:27 AM UTC

Actually its there in the OOTB workflow process... When language copy is created and sent for translation(TranslateLanguageCopyProcess),   traverseAndTranslateParent(result, inputResource, tSvc); is recursively called and hence all parent pages are also sent for translation 

Translate
Sham_HC
Sham_HC
Level 10
Oct 16, 2015 2:27 AM UTC

Sounds like a custom implementation issue.  can you provide more details to reproduce the same in fresh vanilla instance without custom code?

Translate
Terms & ConditionsAccessibility statement

Loading footer...