Studio 2011 SP1 & Trados 2007 bilingual files – Part IV

After explaining in my previous posts how to adjust the compatibility settings for TTX, how to handle bilingual .doc files in Studio, how to deal with TTX files in Studio, let’s have a look at a last scenario.

Scenario 3: Client sends new source files and wants translated files and TTX files back

No need to say that you could create TTX files using Trados 2007 and follow Scenario 3 as explained in my last post but my intention here is to present a new working method introduced thanks to the SDL OpenExchange program. OpenExchange is an initiative launched by SDL to promote the development of Apps able to add new functions to SDL Trados Studio. Most of those Apps are free and some of them are now fully integrated in Studio “from factory”. The platform offers many useful plug-ins: TM & format converters, a batch search & replace applet, multilingual dictionaries, etc. One of the most important App is, no doubt, SDL TTX IT which batch converts files to TTX format without having to use Trados 2007.

Suppose that your client sends you source files and wants translated files and TTX files. SDL Studio now works with .sdlxliff files (and not TTX as in SDL previous versions). Nevertheless, TTX format is still one of the most widely used formats by LSP’s. Well, here is a quick workaround to create TTX files. After translation in Studio, you can easily return TTX files to your client using this workflow:


1. Open TTX IT from the Start menu under SDL > SDL Trados Studio 2011 > OpenExchange Apps > SDL TTX IT.

2. Select the source language in the Source language box.

3. Click on Filters to adjust the settings according to the files you want to convert.

Note: Only the formats supported by Trados 2007 are supported by TTX IT. Examples of formats not supported: FrameMaker MIF, InDesign IDML, Office 2010 files, etc.

4. If you need to convert a file associated to an INI file, load the INI file pressing the INI Files button. The usual Trados 2007 Tag Settings window displays.

Note: If you use INI files to create the TTX files, you will have to create new file types in Studio based on those INI’s to display correctly the files in Studio.


In this step, decide whether you want to use smart tag pairing or full compatibility mode for TTX files and define the tag verification settings for TTX. If you don’t know how to proceed, see my previous post to learn how to change the compatibility settings for TTX.


Translate in Studio as explained in my post on how to deal with TTX files in Studio.


1. Select File > Save Target As from the Studio menu to generate the target translated document for a single file. Select TRADOStag Document in the following dialog box. The result is a fully translated TTX file.

2. If you are working with a project, select Project > Batch Tasks > Finalize from the Studio menu. The Finalize task generates TTX files in the target folder of your project.

3. Deliver the completed TTX files to your client.

For more complex scenarios, please see how to deal with TTX files in Studio.


Thanks to this workaround, you can quickly create TTX files from source files, take advantage of all the Studio functionality, such as Autosuggest, auto-propagation, etc. and deliver TTX files and translated files as requested by your client.


Here is a summary of all the possibilities and the workflow to use for all the scenarios and cases we have seen in my last four posts on Studio 2011/Trados 2007 interoperability.


5 responses to “Studio 2011 SP1 & Trados 2007 bilingual files – Part IV

  1. Pingback: SDL Studio to Trados Legacy Converter | Translation Tutorials Blog

  2. Pingback: skytherock

  3. Pingback: SDL Studio to Trados Legacy Converter | skytherock

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s