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

  • When users want to translate Structure Groups separate from Pages, is it always in separate translation jobs or might they sometimes want Structure Groups AND Pages in the same job?

    And what are they trying to accomplish when translating Structure Groups?

    For example, I'd often use Structure Group fields for translatable content related to website navigation. In this case, what users really want to translate would be all the Structure Groups related to navigation (site navigation,  secondary navigation, breadcrumbs, site map, etc.). In this case, I'd focus on some type of "translate navigation" setup in the implementation using things like the event system, workflow, and/or advanced search.

    Thinking Lars point through, I can imagine the "complete" setup for options for each type of item would also include checkboxes for nested organizational items (think Content Porter's selection options). :-O

Comment

  • When users want to translate Structure Groups separate from Pages, is it always in separate translation jobs or might they sometimes want Structure Groups AND Pages in the same job?

    And what are they trying to accomplish when translating Structure Groups?

    For example, I'd often use Structure Group fields for translatable content related to website navigation. In this case, what users really want to translate would be all the Structure Groups related to navigation (site navigation,  secondary navigation, breadcrumbs, site map, etc.). In this case, I'd focus on some type of "translate navigation" setup in the implementation using things like the event system, workflow, and/or advanced search.

    Thinking Lars point through, I can imagine the "complete" setup for options for each type of item would also include checkboxes for nested organizational items (think Content Porter's selection options). :-O

Children
No Data