Translation BluePrint best practices
This section provides recommendations on the design of your BluePrint for Translation Manager.
In your Translation BluePrint you need to take account of the following:
- Do not mix languages in a single Source Publication—a Publication is assigned a single translation language when you configure a Publication for Translation.
- Create a language layer in your BluePrint with Publications configured as Target Publications that contain only translated content to:
- create a clean distinction between translated content and local content added by content authors and
- allow you to re-purpose content to other channels, for example an email campaign
- Create Child Publications under Target Publications in your language layer and create local Folders and Structure Groups in this Publication in which content authors can add local content.
- By default, SDL TMS is the owner of the translated content, which means that if you update a translated item (local copy) in Content Manager Explorer, sending the item out for translation again will overwrite these changes, because the Translation Memory has no knowledge of the update. One way to guard against this problem if content authors are permitted to add local content in a Target Publication, is to create clearly marked local Folders and Structure Groups in which content authors can add local content. You can assign users and groups specific permissions to define user access to Folders, Structure Groups, and Categories to ensure that content authors do not update translated content. Another way to combat this problem is to enable the Review feature, which lets SDL Web authors review the segments (drafts) before the translation is finished and modify them as needed. That way, the desired modifications are saved to Translation Memory.