Documentation Center

Translation entry locking and auto segment locking

WorldServer allows you to create projects that restrict updates to certain segments. The restriction is accomplished by using the segment locking feature within workflow steps where segment locking is enabled. The objective is to safeguard certain changes to translations made by language specialists (LSs), when those translation need to be protected. A typical process might look like the following:
  1. A language specialist identifies a translation that needs to be corrected. To safeguard the change, the LS locks the segment. The LS must correct and lock each occurrence of the segment across all assets that contain it.
  2. When the updated translation is saved to the TM, this lock status must be transferred to the TM.
  3. When an asset is leveraged, the segment needs to be locked automatically if the match is an ICE or SPICE match and the TM entry is locked.
  4. If the segment is unlocked explicitly (or programmatically), then saving it to the TM should remove the lock from the associated TM entry.
Locking translation entries
Translation entries contain a lock status. You can set the status explicitly by using the TM entry edit tool and selecting or clearing the lock translation option. The TM entry can be locked automatically by locking an updated segment and saving the translation to the translation memory. When a new TM entry is created , it inherits the lock status from the segment that was used to create the TM entry. While you can lock at TM entry by locking a segment, you cannot unlock a TM entry by unlocking the segment. Additionally, the ability to lock a TM entry by locking a segment can be configured using the enable_tm_entry_locking_for_locked_segments TM property. This property is enabled by default. By setting it to false, segment locks will not be transferred to the TM entry.
Segment auto- locking
Asset segments can be locked directly. Locking or unlocking segments directly requires opening an asset in a WorldServer translation workbench via a human step that has step locking enabled. With the support of translation locking, asset segments can be locked automatically when ICE leveraged against locked TM entries. Users cannot modify the translation within the browser workbench if a segment is locked. Depending on the available options, the user might be able to unlock the segment. Only when the segment is unlocked can the translation be updated.
Segment auto-locking does not happen automatically. It requires the specific auto-segment locking condition to be enabled. The following configuration options are all set to false by default:
  • If a SPICE match results and the TM entry is locked. Configure the TM property:
  • enable_auto_segment_lock_on_locked_spice_match= false|true
  • If an ICE match results and TM entry is locked. Configure the TM property:
  • enable_auto_segment_lock_on_locked_ice_match= false|true
  • ICE match with locked TM entry from same asset. Configure the TM property:
  • enable_auto_segment_lock_on_locked_ice_asset_match= false|true
Summary of support
Locking an updated segment and saving the translation to the TM results in the TM entry being locked.
Unlocking the segment and updating the translation unlocks the TM entry when the translation is saved to the TM.
Leveraging a locked TM entry results in the asset segment being locked when the match results in an SP/ICE match depending on the auto locking option enabled. In WorldServer 8.0, there are three new TM configuration options for controlling segment auto locking. They are all set to false by default.