Translation Flow and Integration Improvements
Some improvements and changes are specific to Translation Management and Translation Organizer.
General
Translation Management has been fully refactored, resulting in stability and performance improvements. On top of this we made sure that IWrite* plugins now also runs on the newly created target languages. The source language used for the generated target languages is better controlled by the introduction of <languagepaths>.
Event types
The background tasks/event types for Translation Management have changed, and one (DELETETRANSLATIONS) have been removed. The Event Data for these event types has also changed.
| Event Name | Description | Event Data Sample |
|---|---|---|
CREATETRANSLATIONFROMREPORT |
| |
CREATETRANSLATIONFROMLIST |
| |
CREATETRANSLATION |
| |
Combining this revisited granularity of having many CREATETRANSLATION as early as possible and the introduction of Background in the previous release, we greatly boosted throughput and introduced extra scaling options on top.
Language paths
It is now possible to define preferences in source language for translations. This is determined by the top-down succession order of the <languagepath> elements. When a path is specified first, it will be applied in priority. For example, the paths define that when it comes to translate content into fr, the source language will be es in preference to en, because the path from es to fr is specified first. On the other hand, es can only be created from en.
<languagepaths>
<languagepath from="es" to="fr" />
<languagepath from="en" to="es" />
<languagepath from="en" to="fr" />
</languagepaths>
Resolution control on the Translation Job
You can now control which Image resolutions are being generated by Translation Management to be pushed out by the Translation Organizer service. Do note that Translation Management should be enabled on the image objects in question. [TS-9096|TS-8999|SRQ-2510]
File System enabled out-of-the-box
In the past you had to configure either WorldServer, TMS or file system to work. From now on, TranslationOrganizer.exe.config has file system readily configured for usage. [TS-8992]
Translation Management on Images
The logical level Translation Management flag (FNOTRANSLATIONMGMT) on images was not respected. When Translation Management is enabled it should not be possible to manually add language/resolution combinations. When Translation Management was triggered on the image, it resulted in error Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another near Generating mixed language file. The implementation of RunTranslationManagementOnResolution was corrected. [TS-8940|TS-8910|SRQ-2574]
Translation Organizer
Introducing support for WorldServer 11 and TMS 11.
In essence Translation Organizer does database (repository) to database (translation management system) synchronization. We optimized the routines and introduced better debugging support. Retry routines are tuned towards our repository and towards WorldServer and TMS - for example when synchronizing templates. The routines of unleasing Translation Jobs are tuned to make sure jobs always keep moving.
Translation JobProperties will now show the Leased by and Date leased on fields for informational purposes.
EventMonitor entries are no longer deleted if they are connected to an incomplete Translation Job entity.
Other
As all other processes, Translation Management benefits from the fact that now all API25 methods accept element names. This means that developers can change user role labels as they go along.
As other processes, Translation Management benefits from the Background tasks polling system. Translation tasks can be carried out in parallel with publication, synchronize and other tasks. The delay before the tasks are started is also reduced.