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 a similar problem when we want to send selected structure groups only to translation for breadcrumbs. As an example, when we created a translation job for 24 structure groups in Sites with the first checkbox selected, translation jobs in TMS contained 498 structure group files and 246 page files instead of 24 structure group files. We need a way to send 24 structure files only to TMS without sending sub structure groups and pages from Sites. Because of this limitation, our current process is all manual - copying and pasting content from Sites into a separate file, sending the separate file to translation and coping and pasting translated content back to Sites language by language. Can you split the option for organizational items into "selected" and "nested" to be more consistent with other content types? Can you also make option names consistent across the content types so that we do not have many checkboxes when the multiple types are added to a single translation job?

    The idea of checkboxes per content type would be like this:

    •  Page:
      1. Translate selected item:  Translate page
      2. Translate nested content items: Translate components on the page
    •  Category:
      1. Translate selected item:  Translate category
      2. Translate nested content items: Translate nested keywords
    • Organizational Item (Bundle, Structure Group, Folder, etc.):
      1. Translate selected item: Translate selected organizational item 
      2. Translate nested organizational items: Translate nested organizational items 
      3. Translate nested content items --> Translate non organizational items for example, pages, components, etc. contained in organizational items

      

Comment

  • We have a similar problem when we want to send selected structure groups only to translation for breadcrumbs. As an example, when we created a translation job for 24 structure groups in Sites with the first checkbox selected, translation jobs in TMS contained 498 structure group files and 246 page files instead of 24 structure group files. We need a way to send 24 structure files only to TMS without sending sub structure groups and pages from Sites. Because of this limitation, our current process is all manual - copying and pasting content from Sites into a separate file, sending the separate file to translation and coping and pasting translated content back to Sites language by language. Can you split the option for organizational items into "selected" and "nested" to be more consistent with other content types? Can you also make option names consistent across the content types so that we do not have many checkboxes when the multiple types are added to a single translation job?

    The idea of checkboxes per content type would be like this:

    •  Page:
      1. Translate selected item:  Translate page
      2. Translate nested content items: Translate components on the page
    •  Category:
      1. Translate selected item:  Translate category
      2. Translate nested content items: Translate nested keywords
    • Organizational Item (Bundle, Structure Group, Folder, etc.):
      1. Translate selected item: Translate selected organizational item 
      2. Translate nested organizational items: Translate nested organizational items 
      3. Translate nested content items --> Translate non organizational items for example, pages, components, etc. contained in organizational items

      

Children
No Data