Under Community Review

Wouldn't it be better if the translation systems have a more effective UI for handling many small files?

Configuration of translation task aggregation

We recently upgrade from Tridion 2013 to Web 8.5. Something that we found to be different between the two versions is with Translation Manager and aggregation of components into tasks.

The translators at our company find it better to translate with context if all the components that are added to a translation job create a single task if aggregation is selected. This is the functionality as of Tridion 2013.

After the upgrade, only components with like sachems will be "stitched" together as grouped components in separate tasks within WorldServer. A configuration that would allow for a single task to be created with all components marked for aggregation would make it simpler for translators to pick the task that has the content, with context, that they need to translate.

Trevor Bartlett
Parents

  • A better long term solution would be for the translation systems to have an efficient UI for dealing with translating many small files with just a few translatable strings in each (so translation optimized for data repositories, not just for typical documentation style tasks). Then aggregation could be removed completely.

Comment

  • A better long term solution would be for the translation systems to have an efficient UI for dealing with translating many small files with just a few translatable strings in each (so translation optimized for data repositories, not just for typical documentation style tasks). Then aggregation could be removed completely.

Children
No Data