Trados TagEditor XML (TTX) files are bilingual files created in SDL Trados 2007 Suite or earlier. They are still very much in use as an exchange format to address compatibility issues between SDL Trados versions. They also enable other Translation Environment Tools to work with SDL Trados projects. Transit NXT can easily convert TTX files to Transit’s internal working format so that you can work with projects created in SDL Trados. We will show you how and what you have to bear in mind. First, it’s important (and useful) that the match value be set to 100% in the TTX file when creating it — we will see below why. The option Segment Unknown Sentences must also be selected in TagEditor when creating the TTX file.
The TTX file’s target segments may contain the translation or not, and that determines how you use the converted language pair that you obtain. You might use it as reference material (i.e. Transit NXT’s translation memory) if it is fully translated, but you will keep it as a working file for the project if it is only partially translated or not translated at all.
First of all, let’s see how to convert it (or, in other words, import it). In the project settings, tab File type, select the format Trados TTX.
Press the Options button to open the file-type settings dialog, where you must select the first option: Use pretranslated segments from TTX files and skip Transit pretranslation. This option ensures that the content of the translated target segments in the TTX is maintained.
After the import, you may open the language pair and view the result. Let’s have a look at our French to Italian example:
Open the converted TTX file as a Transit NXT language pair
Here we see that segment 9 is not translated and only segment 5 is confirmed, although segments 3 and 7 are translated as well. The fact that there are segments which are not confirmed means that the match value in TagEditor was not set to 100%. In such cases, you have a couple of options: to ask the client to generate the TTX file again, marking the right option, or translate the file in Transit NXT as it is. In the latter case, obviously you would only need to confirm the translation in those segments where the Italian text is already there.
Or, if you know for sure that all segments are translated, you can confirm them all in one go in the menu Review | Proofreading | File status: Translated, which is faster that confirming one by one.
Just a reminder about why it is important to confirm segments. Apart from it being a sign that the translator regards the segment’s content as the final translation, there’s a practical reason too: translated segments in Transit NXT must be confirmed so the file can be used as reference material later on.
For more information, we recommend that you have a look at the Filters and Supported File Formats guide in http://www.star-group.net | Downloads | Transit & TermStar NXT | Technical Documentation.
Remember, we have stepped up the publishing frequency of the Tooltips blog. From now on, there will be one post every week, so make sure you visit regularly. Last but not least, a special thanks to Karen Ellis for reviewing this post.