Live TM mode

As of WorldServer 9.0, you can choose how you want users to update translation memories: either dynamically, as they translate (Live TM mode) or statically, when they select a button (Non-Live mode). By default, WorldServer runs in Live TM mode, because this enables users to share the same translation memory in real time or near-real time.

In Live TM mode, entries are added to the translation memory during the translation process and WorldServer tracks the status of these entries to distinguish between them. Translation memories are updated whenever a user performs an operation that updates the segmented cache – for example, saving to the Asset Interface System (AIS) or importing offline work.

The combination of Live TM mode and segment status make it possible for translations to go into the translation memory as soon as possible for the benefit of all translators. At the same time, translators can distinguish between translations that have been reviewed and those that might just have been added.

The translation status of a segment can be different from the translation status of a TM entry. As translators work, the source and target text are copied from the segment cache to the translation memory. Segment translation status determines if a segment is added to or updated in the translation memory and what translation status the corresponding entry should have. The following table shows what happens to the status of the TM entry when a user changes the translation status of a segment in Browser Workbench:
Segment translation statusAdd or update made in the TM?TM entry translation status
NoneYesPending Review
Pending ReviewYesPending Review
ReviewedYesReviewed
RejectedYesRejected

When WorldServer first segments your file and creates the bilingual segment list, it tries to find translations in your translation memory. If it finds an ICE match or a 100% match, it inserts them automatically. By default, only TM entries with the Reviewed status can result in ICE matches.

If WorldServer finds an ICE match, it inserts in into the target segment and automatically sets the translation status of the segment to Reviewed. If WorldServer finds a 100% match, it inserts it into the target segment and automatically sets the status of the segment to Pending Review.

After a translator translates a segment and selects Save, the translation goes into the translation memory with the Pending Review status. Later, if a reviewer changes the status of the segment to Reviewed and selects Save, the corresponding entry in the translation memory is also set to Reviewed.

By the end of the workflow, all segments should have a Reviewed status in the translation memory.

Other properties for Live TM mode

In addition to the enable_live_translation_memory and maximum_exact_translation_status properties, there are two other properties in the tm.properties file that you can use to control the behavior of Live TM mode:
  • require_reviewed_status_for_ice=true: Determines if TM entries must have the Reviewed status as a requirement for ICE matches. The default behavior is that unreviewed TM entries do not meet the criteria for ICE matches. To make Pending Review TM entries with ICE match scores have their segment translation status set to Pending Review (instead of Reviewed), uncomment this property and set it to false. In Non-Live mode, all TM entries are reviewed, so this configuration does not affect ICE matches.
  • tm_score_unreviewed_match_penalty=0: Defines the penalty for TM matches with an unreviewed translation status. In Non-Live mode, all TM entries are reviewed, so this configuration does not affect ICE matches. This is a leverage-level penalty. It is applied to the final score produced by the match and only during leverage-based processes. Set the value between 0 and 1. This penalty applies to all TM matches.
By default, these properties are commented out. To apply them, uncomment them, specify appropriate values, and restart WorldServer.