P R O F E S S I O N A L    L I C E N S E S

This Studio Plugin allows you to add server-based termbases to a Trados Studio project as a local termbase which can be taken off-line or even sent to the translators. It can optionally scan the source documents for terms that exist in the termbase and then adds only the relevant ones to the project specific local termbase. Furthermore, you can filter down the data on an entry and even a field level.

The configuration can be stored and then included in project templates, for instance. This allows you to automate the entire process of creating project termbases.

Together with quickTerm and the quickTerm Studio Plugin, you can then also use offline workflows such as term requests in Studio. This module, however, has to be installed and licensed separately.

Excelling Studio organizes your Excel files and prepares them for translation in SDL Trados Studio. The tool reads data from the columns and rows of excel files and converts them to a special XML format. During pre- and post-processing of the files there are a lot of options you can set up. For instance:
• you can merge several columns or even rows in the source excel into one logical segment in Studio. This is useful, for instance, if some database export contains several fields, which logically form one segment in Studio. The cells from the source excel are then separated by a break tag in Studio, but can be translated as one unit. The length verification can be done either for each "cell", or for the total segment.
• you can define, in which columns the source language can be found, and what target languages should be imported into what cells after translation.
• you can have the tool check if there is already a translation in the target cells. If so, you can define if this translation shall be exported to Studio, too, or if it should be ignored. You can even lock these translations in Studio automatically. This feature of exporting the target languages, too, can actually be used as an elegant alignment workflow, since SDLXLIFF files can be directly imported into Studio. you can optionally read the target language from one column but write it back to a different one.
• you can define where comments can be found. These comments will then be displayed in Studio as comments.
• you can automatically generate projects for many excel files which always follow a certain naming convention. This is done by mapping export/import tasks to particular filename pattern, thus enabling export/import of an entire directory.
You can save the export/import definition as a "task" which you can always run again for identical excel files.

Excelling  MultiTerm is an interface between MS Excel and SDL MultiTerm. It is used to edit termbase data offline in Excel and import it back to MultiTerm.

Excelling MultiTerm lets you precisely select data from MultiTerm and export that data into an Excel file. Once in Excel, you can then edit, translate, or review your terminology. You then use the Excel file itself to update the data in MultiTerm.

You can also use Excelling MultiTerm to create new entries in MultiTerm from an Excel list. Excelling MultiTerm also contains a number of features which professional users of MultiTerm will find very useful for maintaining their termbases.

The single license allows installation on only one PC. The concurrent license allows the software to be installed on several PCs simultaneously. Only one user can actually use the software concurrently.

Publishing MultiTerm is the ideal add-on if you want to publish your terminology as a glossary, or if you want to export your data for re-use in other systems.

Use Publishing MultiTerm to select specific content from SDL MultiTerm termbases and convert the selected data to either PDF layout or XML for use in other systems.

The concurrent license allows the software to be installed on several PCs simultaneously. Only one user can actually use the software concurrently.

Splitting TTX is a tool for splitting large TTX files into several smaller TTX files. After translation, these pieces can be merged back into one TTX file.

This is particularly useful when a TTX file is too large to handle efficiently in TagEditor or when several translators will work on one source file.

As the name implies, Splitting TTX currently handles only TTX files. A version for handling SDLXLIFF files is under development.

Some content management and technical authoring systems, such as Fischer TIM-RS, will output XML content without line breaks (CR Linefeed). This creates problems when translating the file in TagEditor because the text becomes highly unorganized and performance drops significantly.

Fragmenting XML solves this problem by allowing the user to insert line breaks in front of certain elements and then remove those breaks after translation is complete.

Checking Duplicates is designed to search translation memories and termbases for duplicates that the standard-issue SDL functions will not find.

With secureSDLXLIFF you can check for known issues and pitfalls in various document types, most prominently Microsoft Word, but also file types like Excel or InDesign.

When switching from SDL Trados 2007 to SDL Trados 2009, many companies face the challenge of backwards compatibility. The reason is that often times there are still translators working in the older 2007 version who nevertheless need to be used in the workflow and need to be given translation memories. SDL Trados 2009 does offer a TMX export for these cases. However, the encoding of text and attribute fields is different in the 2009 TMX export than 2007 requires it for import. Therefore these text and attribute fields are lost when importing the TMX file into the 2007 Workbench.

FixingTMX solves this problem.

goAnalyze . Our Analysis tool for SDL Trados Studio. Analyze files via context menu or drag and drop without creating projects first.
goAnalyze is a Trados Studio add-on which allows you to perform an analysis of several or even zipped files without having to open them in Trados Studio.
Before running the first analysis, you create profiles in the user interface of goAnalyze. These profiles consist of the language combination, the translation memories to be used plus optional analysis settings.
Then you can start an analysis by doing one of the following:
▪ Drag and drop one, several or zipped files onto the desktop icon and then select the analysis profile you want to use.
▪ Right-mouse click the file(s) and start the analysis from the context menu.
The analysis results are stored to a file according to the settings you have provided in the beginning. All temporary files will be deleted automatically. Studio does not have to actually run on the machine, but it needs to be installed.