RWS Community
RWS Community
  • Site

Trados Studio

Trados Enterprise

Trados Team

Trados GroupShare

Trados Business Manager

Passolo

MultiTerm

RWS AppStore

Connectors

Beta Groups

Managed Translation

MultiTrans

TMS

Trados Enterprise

WorldServer

Language Weaver

Language Weaver Edge

Language Weaver Connectors

Language Weaver in Trados Studio

 

 

Tridion Docs

Tridion Sites

LiveContent S1000D

XPP

Language Developers

Tridion Docs Developers

Community Help

RWS User Experience

AURORA

Internal Trados Ideas

Mercury

RWS Community Internal Group

XPP Cloud

Language Combinations by Language Services

RWS Training & Certification

Style Guides

RWS Campus

Trados Approved Trainers

ETUG (European Trados User Group) Public Information

Nordic Tridion Docs User Group

Tridion West Coast User Group

Trados Studio Ideas

Trados GroupShare Ideas

Trados Team Ideas

Trados Team Terminology Ideas

Trados Enterprise Ideas

Trados Business Manager Ideas

MultiTerm Ideas

Passolo Ideas

RWS Appstore Ideas

Tridion Docs Ideas

Tridion Sites Ideas

Language Weaver Ideas

Language Weaver Edge Ideas

Managed Translation - Enterprise Ideas

TMS Ideas

WorldServer Ideas

Trados Enterprise Ideas

LiveContent S1000D Ideas

Contenta S1000D

XPP Ideas

Events & Webinars

RWS Training & Certification

To RWS Support

  • Search
  • Translate

    Detecting language please wait for.......


    Powered by
  • User
  • Site
  • Search
  • User
  • Product Groups
  • Trados Portfolio
  • RWS AppStore
  • More
  • Cancel
RWS AppStore

RWS AppStore > Wiki

TM Optimizer
  • Home
  • Forums
  • Wiki
  • More
  • Cancel
  • New
Show Translation Options

Detecting language please wait for.......


Powered by
RWS AppStore requires membership for participation - click to join
  • -RWS AppStore
    • +AdaptiveMT Trainer
    • +Amazon Translate MT provider
    • +Antidote Verifier
    • +Apply Studio Project Template
    • +ApplyTM template
    • +AppNotifications
    • +AutoHotKey Manager (AHK)
    • +CleanUp Tasks
    • +Community Advanced Display Filter
    • +DeepL Translation Provider
    • +DSI Viewer
    • +Excel Terminology Provider / TermExcelerator
    • +Excel4GroupShare
    • +Trados Studio – Export Analysis Reports
    • +Export To Excel
    • +Fail Safe Task
    • +Google API Validator
    • GroupShare Kit
    • +GroupShare Version Fetch - Authentication options
    • +Hunspell Dictionary Manager
    • +IATE Real-Time Terminology
    • +IRIS PDF OCR Support for Studio
    • +Lingotek TMS plugin for Trados Studio
    • +MEMSOURCE CloudTM Provider
    • +MT Comparison
    • +MT Enhanced Plugin for Trados Studio
    • +MXLIFF File Type Support
    • +PA Admin
    • +Post-Edit Compare
    • +projectTermExtract
    • +Qualitivity
    • +Rapid Add Term
    • +RecordSource TU
    • +Reports Viewer Plus
    • +Trados Data Protection Suite
    • +Trados Freshstart
    • +Trados LegIt!
    • +Language Weaver
    • +Language Weaver Edge
    • SDL MultiTerm Extract
    • +MultiTrans Plug-in for Trados Studio
    • +Trados Studio InQuote
    • +Trados T-Window for Clipboard
    • +Trados TMBackup
    • +Trados Studio Word Cloud
    • +Trados TTS
    • +SDLTM Import Plus
    • +SDLXLIFF Convertor for MS Office
    • +SDLXLIFF Split / Merge
    • +SDLXLIFF to Legacy Converter
    • +SDLXLIFF Toolkit
    • +Signoff Verify Settings
    • +Star Transit (TransitPackage Handler)
    • +Studio Migration Utility
    • +Studio Subtitling
    • +studioViews
    • +Stylesheet Verifier
    • +Target Renamer
    • +Trados Copy Tags
    • +Target Word Count
    • +TM Lifting (ReIndex Translation Memories)
    • -TM Optimizer
      • Archived Versions: TM Optimizer
      • ChangeLog TM Optimizer
    • +Trados Analyse
    • +Trados Batch Anonymizer
    • +Trados InSource!
    • +Trados Number Verifier
    • +Trados Transcreate
    • +Wordlight
    • +WorldServer Compatibility Pack for Trados Studio
    • +XLIFF Manager for SDL Trados Studio
    • +XML Reader
    • +#YourProductivity
    • +File type definition for TMX
    • +File Type Definition for Wordfast TXML
    • +Google Cloud Translation Provider
    • +Jobs
    • +Microsoft Translator Provider
    • +MSWord Grammar Checker
    • +Multilingual Excel Filetype
    • +Multilingual XML FileType
    • +OpenX Hash Generator
    • +PDF Assistant for Trados
    • +RWS Community Inside
    • +SDLTM Repair
    • +SDLXLIFF Compare
    • +Segment Status Switcher
    • +Studio Time Tracker
    • +TermInjector
    • +TMX Translation Provider
    • +Trados 2007 Translation Memory Plug-in
    • +Trados Compatibility and Migration Power Pack
    • +Trados QuickInfo
    • +Trados Translation Memory Management Utility
    • +TuToTm
    • +Variables Manager for Trados Studio

TM Optimizer

In this section:

  • Using TM Optimizer
  • How does TM Optimizer work? 

Using TM Optimizer

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:

  1. Convert Workbench translation memory: Use this option when you have not yet converted your Workbench TM for use in Studio. You will need a TMX export of the Workbench TM you want to convert.
  2. Optimize already converted Workbench translation memory: Use this option when you have already converted your Workbench TM to a Studio TM but are having problems caused by excessive formatting tags. You will need your Studio TM and a TMX export of your original Workbench TM. 

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.

 

How does TM Optimizer work?

Increases TM leverage

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. 

Removes excessive formatting, e.g. font change, kerning, tracking, spacing

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.

Import of the TMX is much faster

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%.

Makes migration from DOC in TagEditor to DOCX in Studio much easier

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.

Workbench Analysis Results
Analysis results of a DOC test file against the original TRADOS Workbench TM:

  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Our Terms of Use
  • Copyright
  • Privacy
  • Security
  • Anti-slavery Statement
  • Cookie Notice
  • YouTube