TTX is a Trados bilingual file format supported by MemSource.
Pre-segmenting TTX Files
MemSource will only import those segments from a TTX file that have been pre-segmented in Trados. Therefore, it is necessary to first pre-segment the TTX file and then import it into MemSource.
This is how to pre-segment TTX files in SDL Trados:
- Open SDL Trados Translator's Workbench
- Go to File - New - Create... and create a translation memory
- Then click on Tools - Translate... and use the Add... button to add the TTX file you wish to pre-segment
- Make sure that the option Segment unknown sentences is selected
- Hit the Translate button
- Import the pre-segmented ttx file into a MemSource project
Note: If there is a trados.ini file attached, make sure it is in the same directory as your ttx file during pre-segmentation.
Respecting TTX Language Specification
Make sure that you exactly match the language codes of the TTX file with the language codes of your MemSource Project. E.g., if your TTX file has "EN-US" as target language, you have to select "English-United States" also in MemSource as the project's target language (not just "English"). If you fail to do so, your existing translations in the TTX file may fail to import into MemSource.
A segmented TTX is a bilingual file format and it may already include translations with a corresponding match percentage. If that is the case, the translations are treated in the following way by MemSource:
- All translations get carried over to the MemSource XLIFF (MXLIFF) bilingual file format
- 101% matches coming from the TTX are displayed as 101% matches in MemSource and the segment status is set to confirmed
- 100% matches coming from the TTX are displayed as 101% matches in MemSource and the segment status is set to unconfirmed
- Fuzzy matches (anything below 100%) coming from the TTX are displayed as fuzzy matches in MemSource with the corresponding match percentage and the segment status is set to unconfirmed
Important Notice on Translating TTX Files in MemSource
While TTX files can be imported into a MemSource project, we typically do not advise our customers to translate these formats in MemSource as their standard practice. The reason is that these formats are proprietary and can be best translated by SDL software that has been designed for it. There may always be minor or even major incompatibilities when translating Trados bilingual files in a non-Trados software.
Also, there are important benefits that a user has to give up when translating TTX files instead of the actual source files in MemSource. When a user imports a file for translation (e.g. MS Word) into a MemSource project, MemSource automatically pseudo-translates the file in the background and checks if it can be correctly exported and opened in the MS Word application. If this test fails, the file is disabled for translation until the problem has been fixed. This is a great feature because in this way we can provide a guarantee to our users that the files they import into MemSource can also be exported back and opened in their native application. We cannot provide this kind of guarantee with TTX files.