Documentation Center

What's new in Translation Manager 2011 SP1

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

Integration in SDL Tridion suite
Translation Manager is now fully integrated into the SDL Tridion suite. You install Translation Manager using the suite installer.
Integration in Tridion Database Manager

You can install/upgrade the Translation Manager database using the Tridion Database Manager tool.

Excluding already translated items
By default, Translation Manager does not send items included in a Translation Job to translation if the item has not changed since it was last sent. You can override this behavior by selecting the Include already translated items check box, for example if you were not satisfied with the translation.
Configuring translations at Folder, Structure Group or Category level
In your translation BluePrint hierarchy, you can now configure Folders, Structure Groups or Categories as well as Publications for translation. You can configure source content at a global level by configuring the Publication or, if you want finer-grained control over what content is translated and into what languages, you can configure Folders, Structure Groups and Categories.
Translating Keywords
You can now translate individual Keywords or a whole Keyword branch.
Defining translatable fields in Schemas
You can now control what fields are sent to translation by configuring your Schemas and Metadata Schemas:
  • In the General tab, you can select Translate Name if you want the name of the Component/Folder/Structure Group/Page that uses this Schema or Metadata Schema to be translated, and you can select Aggregate Translation Items if you want to aggregate multiple Content Manager items to be aggregated into a single TMS item instead of separate files for each item.
  • In the Design tab or Metadata Design tab, select the Translatable check box for each text field or external link field that you want to be translated
Translation Manager 2011 SP1 sends translatable fields to the translation system in ITS (Internationalization Tag Set). Only SDL WorldServer 10.1 and SDL TMS version 2011 SP1 onwards provide support for ITS. If you are using a different (supported) version of SDL TMS, you need to use ANL files, Content Types and <ItemTypes> and in the TranslationManager.xml file to filter your content filters.
Security
Translation Manager introduces the following rights that you can assign to groups or users:
  • Translation Management rights — to send Folders and Components, Structure Groups and Pages, Categories and Keywords for translation
  • Translation Configuration rights — to configure Publications, Folders, Structure Groups, and Categories for translation.
In the previous version, a user required Publication Management rights to authorize users or user groups to configure the translation options, and to initiate translations a user or user group was required to be a member of a User Group that you created manually and configured in the TranslationManager.xml.
Translation info
In the Component Info tab you can see whether the current version of the Component has been translated or, if the item has been modified since it was last sent for translation, which version of the item was last translated.
Depending on whether the Component was a source or target for a translation, the tab also displays a link to the Component that was the source for the translation or links to items that were the target for a translation. You can also see which Publication the source or target content is located.
If the content is currently in translation, the tab displays a link to the Translation Job.
Monitoring the status and progress of translations
In the Translation Progress tab of a Translation Job, you can now see which Content Manager items are in which stage of the translation process and the percentage completion for each stage per target language.
Encryption tool
You can encrypt passwords in the TranslationManager.xml configuration file using the encryption tool delivered with Translation Manager.
ErrorEmailNotificationsPlugin.cs sample plugin
The ErrorEmailNotificationsPlugin.cs plugin demonstrates how to send e-mail notifications if errors occur during the translation process.
Translation Manager .NET API
The following changes have been made to the Translation Manager .NET API in classes under Tridion.TranslationManager.DomainModel.Api:
  • TranslationJobManager now implements the System.IDisposable interface. Ensure Dispose is called if an instance of TranslationJobManager is created.
  • PublicationConfiguration is deprecated. It is recommended to use TranslationConfiguration instead.
  • The property ResolvedItemsEventArgs.ResolvedItems is deprecated. It is recommended to use the Items property instead.
The COM-based API is deprecated. It is recommended to migrate code to the .NET-based API.
Changes to TranslationManager.xml
The following configuration options in the TranslationManager.xml file have been removed:
  • <CancelTerminatedJobsInterval>—each Translation Job is now polled for the status of its items using the <TmsPollingInterval> setting, which retrieves items if available, or cancels the job there are no more items in progress.
  • <TranslationAuthorizationGroupUri>—the functionality has been replaced by the new Translation Management right.
The following configuration options in the TranslationManager.xml file have been added:
  • <MaximumTridionItemsPerAggregatedTmsFile>—specifies the number of SDL Tridion items that can be combined into a single file send to the translation management system. If the value is exceeded, multiple files containing aggregated items are added to the Translation Job on the translation management system.

    The setting affects server memory usage as well as how manageable the file is for the translator.

  • <MaximumTridionItemsPerTmsJob>—specifies the maximum number of Content Manager items that can be combined into a single Translation Job on the translation management system.

    The setting affects database transaction time (the number of operations that are performed inside each transaction when the job is send to the translation management system, as well as how manageable the job is for the translator. If the value is exceeded, several jobs are create on the translation management system for the single Translation Job on the Content Manager. The Translation Job will still be managed as a single job in Tridion.

If you are using SDL WorldServer 10.1 and SDL TMS version 2011 SP1, you should no longer use the <ItemTypes> element. If you are using this element, you need to disable it for new translations (it is still required for translations sent with previous versions pending retrieval from SDL TMS).