Translate with Eddy AI only translates content in one direction, from the default (primary) language into secondary languages. If content is created or edited directly in a secondary language, there is no native way to translate it back into the default language. Users must currently rely on an external translation service to manually convert secondary-language content into the default language, which is a manual, error-prone workaround outside the Document360 platform. Suggested Enhancement: Allow Translate with Eddy AI to support translation in the reverse direction, from a secondary language workspace back into the default language, at least as an on-demand action, so users are not forced to leave the platform to reconcile content created in a secondary language. Customer Benefit: Removes the need for external translation tools and manual reconciliation, reduces the risk of inconsistency between the default language and secondary-language content, and gives teams more flexibility in multilingual content workflows where content origination isn't always in the default language.
