Idea Delivered

This automated TM connection is already possible by selecting one of the link options from the Export dialog. Additionally, the default selection on this dialog can be governed by a setting in exchange.properties:

# Controls the TM export type selected by default on WSXZ export. Possible values: content, link, content_and_link. When not set the default is "content".
#export.wsxz.tm.type.default = content

 

Automatic connection to the server-based TMs in Studio

At the moment, there is no automatic connection to the server-based TMs when opening a Translation package in Studio. For every project, the user needs to go to Project settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation > Use... > SDL WorldServer Translation Memory which is time-consuming in terms of project management.

Parents
  • I´m not sure if I´m missing something here, but I think that what you request already works out of the box in WorldServer.

    When you export a package from WorldServer, you can check the "Link" or "Content and link" option in the export dialog. Once you open that package in Studio, a connection to the WorldServer TM will be established automatically. Of course, this applies only to the TM group specified for the particular Project Type.

Comment
  • I´m not sure if I´m missing something here, but I think that what you request already works out of the box in WorldServer.

    When you export a package from WorldServer, you can check the "Link" or "Content and link" option in the export dialog. Once you open that package in Studio, a connection to the WorldServer TM will be established automatically. Of course, this applies only to the TM group specified for the particular Project Type.

Children
No Data