Salesforce

Changes in Japanese/Chinese translation results in SDL Trados Studio 2017 SR1

« Go Back

Information

 
TitleChanges in Japanese/Chinese translation results in SDL Trados Studio 2017 SR1
Scope/EnvironmentSDL Trados Studio 2017 SR1
Symptoms/Context
SDL Trados Studio 2017 SR1 enables upLIFT for Japanese and Chinese translation memories. To enable this, changes in how Studio handles Japanese and Chinese have been implemented. This article aims to give an overview of the consequences of these changes.
Resolution

Matches for Japanese/Chinese Source Language

Opening file-based translation memories from previous version with Japanese/Chinese source language in SDL Trados Studio SR1 will warn that the translation memory needs to be upgraded. You will not receive any matches until you upgrade your translation memory.

Notes for working with Japanese/Chinese source TMs in Studio 2017 SR1:
  • Re-indexing the translation memory enables you to receive matches without upgrading it. However, only re-indexing the TM will not enable you to benefit from the new upLIFT feature and you will continue to receive the warning. We do not recommended this approach.
  • Translation units that have been added, re-indexed or upgraded in 2017 SR1 will not appear in pre-SR1 versions and vice versa. Note: To share translation memories with your co-workers, we recommend SDL Trados GroupShare.
  • When sending packages between Studio 2017 SR1 and previous version, the TM needs to be re-indexed or upgraded after opening the package in order to receive matches.
  • The option Use word-based tokenization for Asian source languages does not affect the behavior described in this article.
 

Context matches

When working with a file-based translation memory with Japanese or Chinese source or target language, generally the following applies after upgrading or re-indexing: Notes:
  • If source language is Japanese or Chinese, the translation memory has to be upgraded or re-indexed for the matches to appear (see above).
  • SDL Development is looking into a solution to recover context matches after re-indexing the translation memory.
Root Cause
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by