SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
After installation, start TM Optimizer from the Start menu under SDL->TM Optimizer.
On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:
On the second page, select the TMX files you have exported from your existing TRADOS Workbench TM. The TMX files are analyzed and the number of TUs and languages are displayed. If you had already converted the Workbench TMs to Studio TMs using the Studio TM upgrade wizard (and have selected option 2 on the previous page), you also have to select that Studio TM here.
On the third page, you select the TM into which the optimized translation units should be imported. This could be either a newly created TM or an existing TM. This TM should be different from the input TM you chose on the previous page.
Finally, on the processing page, you will see detailed progress on the TM optimization process. When all the steps are completed, you can browse to the output TM or open the TM in Studio using the buttons that appear at the bottom of the wizard.
When using TRADOS Workbench with the Microsoft Word macro for translation of RTF and DOC files, translation memories are often polluted with unnecessary formatting tags. If you convert such translation memory into SDL Trados Studio you experience that translations where you expect exact matches will be reported as fuzzy matches, effectively costing you money. TM Optimizer will analyse the content of each translation unit and will optimize the tag content for optimal results in SDL Trados Studio. In addition translation unit content is harmonized so you can achieve the best results and don't spent any extra money on translations you already paid once.
The two screenshots below illustrate what this means in practice. In the first picture, the TM only returns a 99% match where you would have expected a 100% match, purely due to excessive, unnecessary tags.
Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.
Due to limitations of the Microsoft Word macro, unnecessary formatting information is stored in the translation memory. TM Optimizer will remove such formatting giving you less work and making translation easier.
Due the fact that during optimization a vast amount of tags is removed, SDL Trados Studio will perform all operations which are using translation memory much faster. In cetain cases the difference is more than 500%.
More and more clients are migrating from the legacy DOC format towards the latest version of Microsoft Word which is using the new DOCX file format. The features mentioned above will allow you to switch from translating DOC files in Microsoft Word to translating DOCX files in SDL Trados Studio without the major issues with leverage you would otherwise see.
The pictures below show what happens when you move to the DOCX format in Studio, based on a TM that was originally created based on a DOC file using the TRADOS 2007 Word integration. You can see that after applying TM Optimizer, the leverage is almost identical even though we have change file format and TM format.