Salesforce

WorldServer: which Segment Status set in Trados Studio updates the TM when imported as a Return package and what is the correspondent TM entry status and segment status in WorldServer?

« Go Back

Information

 
TitleWorldServer: which Segment Status set in Trados Studio updates the TM when imported as a Return package and what is the correspondent TM entry status and segment status in WorldServer?
URL Name000019133
SummaryWhen working on a WorldServer project created by opening a WSXZ package in Trados Studio, if a segment is changed manually (no matter if the segment is a fuzzy match or a new segment), the content of the target segment will always be imported into WorldServer during the import of the Return package. You can check this by opening the Task in Browser Workbench or Online Editor after the upload/import.

However, you can control whether the Translation Memory will be updated with the content of the changed segment. This article provides more details
Scope/EnvironmentWorldServer
Question
When working on a WSXZ package exported from WorldServer (Live-TM environment or Non-Live TM environment but selecting Update the translation memory using imported assets when importing) which Segment Status updates the TM when importing the Return package and what is the correspondent TM entry status?
Answer
When working on a WorldServer project created by opening a WSXZ package in Trados Studio, if a segment is changed manually (no matter if the segment is a fuzzy match or a new segment), the content of the target segment will always be imported into WorldServer during the import of the Return package. You can check this by opening the Task in Browser Workbench or Online Editor after the upload/import.

However, you can control whether the Translation Memory will be updated with the content of the changed segment. 
  • If you make a manual change to the target segment and set the segment to status Not translated in Trados Studio, the TM will not be updated and the segment will have No Status in WorldServer (when opened in Browser Workbench)
  • If you make a manual change to the target segment and set the segment to status Draft in Trados Studio, the TM will not be updated and the segment will have No Status in WorldServer (when opened in Browser Workbench)
  • If you make a manual change to the target segment and set the segment to status Translation Rejected or Sign-Off Rejected, the TM will be updated with a new TM entry with the status Rejected and the segment will have the status Rejected in WorldServer (when opened in Browser Workbench)
  • If you make a manual change to the target segment and set the segment to status Translated in Trados Studio, the TM will be updated as Pending Review and the segment status will be Pending Review
  • If you make a manual change to the target segment and set the segment to status Translation Approved or Signed-Off in Trados Studio, the TM will be updated as Reviewed and the segment status (when opened in Browser Workbench) will be Reviewed. 
  • If you lock and confirm a segment in Trados Studio, after import, a locked TM entry will be created. If you then unlock the segment, make a change and re-upload the Return package, your change will be written in the target file, but the locked TM entry will NOT be changed. When importing a modified Return package where segments that were locked in a previous import are now unlocked, you will get this warning in the Import window: TM entries for the following segments are locked and cannot be updated: 2 4 (example referring to segments #2 and 4 that were previously locked and created the respective locked TM entries). Note: You can also prevent the locking of the TM entries in general by setting this property to false in tm.properties as follows: 
           enable_tm_entry_locking_for_locked_segments=false

With this property set to false, a "normal" (unlocked) TM entry based on a new translation will always be created even if the translated segment it comes from is locked. The locked segment status will be ignored.
Remember that existing locked TM entries will still not be updated when changing a translation of a target segment whose translation comes from a locked TM entry, for instance as a 100% Match.

For example, if - after segmentation - some of your segments get a 100% or ICE Match from locked TM entries and are pre-translated normally during segmentation if you change the translation of those segments in Studio or Browser Workbench, the locked TM entries will not change or be updated. The change will only apply to the target segment and - after a Save - to the target file. Therefore, if you are not confident that locked TM entries should never be changed, you should set the property to false and - possibly - consider unlocking all existing locked TM entries, following this article:

WorldServer: How to unlock locked entries in a Translation Memory as Batch

See also: WorldServer - if I unlock a locked segment coming from a locked TM entry in Studio, change the translation, confirm and then import the Return package, will the locked TM entry be translated?

If you do not work in Trados Studio, but in Browser Workbench or Online Editor only, please refer to this article:

WorldServer: in a live-TM environment, which Segment Status set in Browser Workbench or Online Editor updates the TM when saved and what is the correspondent TM entry status?
 
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by