What's new in Translation Manager 2013 SP1

This section describes what's new and what has changed in Translation Manager 2013 SP1.

SDL BeGlobal support
You can now send content for translation to SDL BeGlobal.
WebDavURLs in aggregated files
To provide context for a translation, a translation file containing aggregated content includes WebDavURLs for each separate item so that translators can trace text to its source.
Schema validation before sending
Translation Manager now checks whether an item is valid according to its Schema before sending the item for translation, as well as when the item is retrieved from Translation.
Translation Manager checks all items in the Translation Job for validity before sending. If Translation Manager encounters one or more items in a Translation Job that are no longer validate according to their Schemas, the state of the Translation Job will be set to Error sending and no items are sent.
Bundles translation support
Bundles are containers for items in different locations for collective workflow processing or other collective use. You can now send Bundles for translation. The Content Manager items contained in Bundles are resolved when the Translation Job is sent.
Virtual Folder translation support
A Virtual Folder is an item that can contain different types of content items located in different locations in Content Manager. You can now send Virtual Folder for translation. The Content Manager items contained in Virtual Folder are resolved when the Translation Job is sent.
ECL translation support
You can now send the SDL Tridion metadata contained in External Content Library (ECL) Multimedia Components for translation. You cannot add ECL Multimedia Components directly to a Translation Job—you need to add them to a Page or a Bundle and send that for translation.
Changes to SDL WorldServer configuration
When you configure source content, you can now choose to allow users to specify a Project Type when creating a Translation Job, or specify a Project Type for all Translation Jobs as before.
Changes to Retry sending
In previous versions of Translation Manager, the Retry sending action would resend the entire job including all items. You could resend translation jobs that were in the following states:
  • Sending for Translation
  • In Translation
  • Retry retrieving
  • Completed
Resending a Translation Job would start a new translation cycle and remove the connection between the Translation Job in Content Manager and the job on the translation management system, requiring you to delete the ‘orphaned’ jobs manually on the translation system.
In Translation Manager 2013 SP1, Retry sending will now only send items that it had previously failed to send. You can resend translation jobs that are in the following state:
  • Error Sending
Resending a Translation Job now does not remove the connection between the Translation Job in Content Manager and the job on the translation management system, therefore you must not delete jobs on the translation management system when using retry sending. If you do so, these items will not be resent, but result in a canceled job (after any new items are translated).