Under Community Review

Split the Translation of Structure Groups and Pages

With such combination Translation Manager + Worldserver, we want to translate Structure Groups and Pages in different translation jobs, because the most of the pages is not needed to be translated and so we don't want them to get localized.
As you can see in the screenshot a user only has the option to select the translation of structure group and pages. Is there a possibility to split that.



Our thought how that could work the best is that you have three checkboxes (and even more for Bundles for example)

1. Translate structure groups
2. Translate pages
3. Translate components

Paul Brou
Parents

  • We have for a while been considering how we can allow more control over the translation resolving while still maintaining a simple UI.

    The main issue with checkboxes is Bundles would require 6 checkboxes (+/-) - so if you add 10 bundles you would have 60 checkboxes on this screen. If you add a bundle, a page, and a folder you would end up with three items all having different sets of checkboxes available.

Comment

  • We have for a while been considering how we can allow more control over the translation resolving while still maintaining a simple UI.

    The main issue with checkboxes is Bundles would require 6 checkboxes (+/-) - so if you add 10 bundles you would have 60 checkboxes on this screen. If you add a bundle, a page, and a folder you would end up with three items all having different sets of checkboxes available.

Children
No Data