Salesforce

WorldServer - how is an ICE Match segment displayed in Trados Studio once exported from WorldServer as a WSXZ package? Is it possible to change its status from PM (Perfect Match) to CM (Context Match?

« Go Back

Information

 
TitleWorldServer - how is an ICE Match segment displayed in Trados Studio once exported from WorldServer as a WSXZ package? Is it possible to change its status from PM (Perfect Match) to CM (Context Match?
URL Name000021746
SummaryIn WorldServer, ICE Match and 100% Match segments are automatically pre-translated during segmentation. When opening the same Task in Online Editor, those ICE Match segments display as CM (Context Match). Once exported to a WSXZ package, those ICE Match/Content Match segments display as Perfect Matches in Trados Studio. Is it possible to make the segments display as Content Match segments in Trados Studio as well?

Yes, it is possible. This article explains how.
Scope/EnvironmentWorldServer
Trados Studio
Question
In WorldServer, ICE Match and 100% Match segments are automatically pre-translated during segmentation. They display as ICE Match segments in Browser Workbench, as in this example:

User-added image

When opening the same Task in Online Editor, those ICE Match segments display as CM (Context Match)

User-added image

Once exported to a WSXZ package, those ICE Match/Content Match segments display as Perfect Matches in Trados Studio. Is it possible to make the segments display as Content Match segments in Trados Studio as well?
Answer
After exporting a task containing ICE Match segments to a WSXZ package, per default, those segments will be PM (Perfect Match) segments in Trados Studio:

User-added image

However, you can change this behaviour and make the segments display as CM (Content Match) instead. 

There is one setting in FTS, more specifically in the Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config file that controls how those ICE Match segments display in Studio. Per default, it is set to make those segments be set as PM (Perfect Match) segments. On the WoldServer server where FTS is installed, find the Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config file, open it in Notepad++ and find this section in the file:

-->
    <add key='filetypedefinitioncache_max_count' value='256'/>
    <!-- Determines if ice-matches will be exported as perfect matches -->
    <!-- <add key="ExportIceAsPerfectMatch" value="true" /> -->
    <!-- Determines if Studio context matches should be imported back to WorldServer
         as ICE matches. -->
    <!-- <add key="ImportContextMatchAsIce" value="false" /> -->
    <!-- The number of times to retry FTS transactions in the event of database deadlocks or
         communication errors.
     -->

As you can see, this property is set to true per default: <add key="ExportIceAsPerfectMatch" value="true" />. This is the property that sets Ice Match segments to PM (Perfect Match) in the SDLXLIFF file exported with the WSXZ package.

Now change the value of the property to false and add it below the section, like this:

-->     <add key='filetypedefinitioncache_max_count' value='256'/>     
<!-- Determines if ice-matches will be exported as perfect matches -->     
<!-- <add key="ExportIceAsPerfectMatch" value="true" /> -->     
<!-- Determines if Studio context matches should be imported back to WorldServer          
as ICE matches. -->     
<!-- <add key="ImportContextMatchAsIce" value="false" /> -->     
<!-- The number of times to retry FTS transactions in the event of database deadlocks or          
communication errors.      -->

<add key="ExportIceAsPerfectMatch" value="false" />
 

Save your change in the file and restart the SDL File Type Server Service. 

After this change, the CM (Content Match) segment status will be applied to the ICE Match segments in Trados Studio, matching the behaviour in Online Editor as well.

User-added image
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by