<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://uat.community.rws.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer</link><description>This wiki was used to provide helpful information related to the apps from the RWS AppStore. For the latest information please visit https://appstore.rws.com/</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer</link><pubDate>Fri, 12 Jan 2024 16:47:01 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Oana Nagy</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Current Revision posted to Wiki by Oana Nagy on 1/12/2024 4:47:01 PM&lt;br /&gt;
&lt;h4&gt;&lt;strong&gt;IMPORTANT NOTIFICATION:&lt;/strong&gt;&lt;/h4&gt;
&lt;h4&gt;&lt;strong&gt;The RWS AppStore &amp;gt; Wiki is no longer being maintained. For the latest updates and changes being published, please visit the official&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://appstore.rws.com/Plugin/70"&gt;RWS AppStore&lt;/a&gt;,&amp;nbsp;where you will find supporting information such as documentation &amp;amp; change log details that is associated to each app.&lt;/strong&gt;&lt;/h4&gt;
&lt;h4&gt;&lt;strong&gt;Alternatively if you are using Trados Studio 2022 SR2, you will find the same information within the Integrated AppStore.&lt;/strong&gt;&lt;/h4&gt;
&lt;hr /&gt;
&lt;h1 id="mcetoc_1hjv92prf0"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;font-size:inherit;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/1731.pastedimage1548070501380v14.png"&gt;&lt;img alt=" " src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-03-37/1731.pastedimage1548070501380v14.png" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/5633.pastedimage1548070522183v15.png"&gt;&lt;img alt=" " src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-03-37/5633.pastedimage1548070522183v15.png" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/5342.pastedimage1548070538498v16.png"&gt;&lt;img alt=" " src="/resized-image/__size/880x568/__key/communityserver-wikis-components-files/00-00-00-03-37/5342.pastedimage1548070538498v16.png" /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/4338.pastedimage1548070554954v17.png"&gt;&lt;img alt=" " src="/resized-image/__size/886x620/__key/communityserver-wikis-components-files/00-00-00-03-37/4338.pastedimage1548070554954v17.png" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3 id="mcetoc_1hjv92prf1"&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/8686.pastedimage1548070583105v18.png"&gt;&lt;img alt=" " src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-03-37/8686.pastedimage1548070583105v18.png" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hjv92prf2"&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/4212.pastedimage1548070602192v19.png"&gt;&lt;img alt=" " src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-03-37/4212.pastedimage1548070602192v19.png" /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1hjv92prf3"&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id="mcetoc_1hjv92prf4"&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/4555.pastedimage1548070646395v20.png"&gt;&lt;img alt=" " src="/resized-image/__size/1983x988/__key/communityserver-wikis-components-files/00-00-00-03-37/4555.pastedimage1548070646395v20.png" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/6</link><pubDate>Tue, 13 Jul 2021 10:44:09 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Oana Nagy</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 6 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM&lt;br /&gt;
&lt;h1&gt;&lt;span style="font-size:inherit;font-family:arial, helvetica, sans-serif;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/880x568/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/886x620/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1983x988/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/7</link><pubDate>Tue, 13 Jul 2021 10:44:09 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Oana Nagy</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 7 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM&lt;br /&gt;
&lt;h1&gt;&lt;span style="font-size:inherit;font-family:arial, helvetica, sans-serif;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/880x568/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/886x620/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1983x988/__key/communityserver-wikis-components-files/00-00-00-03-36/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/8</link><pubDate>Tue, 13 Jul 2021 10:44:09 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Oana Nagy</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 8 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM&lt;br /&gt;
&lt;h1&gt;&lt;span style="font-size:inherit;font-family:arial, helvetica, sans-serif;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/1731.pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/1731.pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/5633.pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/5633.pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/5342.pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/880x568/__key/communityserver-wikis-components-files/00-00-00-02-17/5342.pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/4338.pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/886x620/__key/communityserver-wikis-components-files/00-00-00-02-17/4338.pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/8686.pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/8686.pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/4212.pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/4212.pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/4555.pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1983x988/__key/communityserver-wikis-components-files/00-00-00-02-17/4555.pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/9</link><pubDate>Tue, 13 Jul 2021 10:44:09 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Oana Nagy</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 9 posted to Wiki by Oana Nagy on 7/13/2021 10:44:09 AM&lt;br /&gt;
&lt;h1&gt;&lt;span style="font-size:inherit;font-family:arial, helvetica, sans-serif;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/1731.pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-03-37/1731.pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/5633.pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-03-37/5633.pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/5342.pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/880x568/__key/communityserver-wikis-components-files/00-00-00-03-37/5342.pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/4338.pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/886x620/__key/communityserver-wikis-components-files/00-00-00-03-37/4338.pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/8686.pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-03-37/8686.pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/4212.pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-03-37/4212.pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-03-37/4555.pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1983x988/__key/communityserver-wikis-components-files/00-00-00-03-37/4555.pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/5</link><pubDate>Tue, 22 Jan 2019 09:11:09 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Florentina Caputa</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 5 posted to Wiki by Florentina Caputa on 1/22/2019 9:11:09 AM&lt;br /&gt;
&lt;h1&gt;&lt;span style="font-size:inherit;font-family:arial, helvetica, sans-serif;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/880x568/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/886x620/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1983x988/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/4</link><pubDate>Mon, 21 Jan 2019 11:49:48 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Florentina Caputa</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 4 posted to Wiki by Florentina Caputa on 1/21/2019 11:49:48 AM&lt;br /&gt;
&lt;h1&gt;&lt;span style="font-size:inherit;font-family:arial, helvetica, sans-serif;"&gt;In this section:&lt;/span&gt;&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;&lt;span style="font-family:arial, helvetica, sans-serif;"&gt;Using TM Optimizer&lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/746x480/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/841x586/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1819x904/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/3</link><pubDate>Mon, 21 Jan 2019 11:37:52 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Florentina Caputa</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 3 posted to Wiki by Florentina Caputa on 1/21/2019 11:37:52 AM&lt;br /&gt;
&lt;h1&gt;In this section:&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="usage"&gt;Using TM Optimizer&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/746x480/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/841x586/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1819x904/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/2</link><pubDate>Mon, 21 Jan 2019 11:37:31 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Florentina Caputa</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 2 posted to Wiki by Florentina Caputa on 1/21/2019 11:37:31 AM&lt;br /&gt;
&lt;h1&gt;In this section:&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="usage"&gt;Using TM Optimizer&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&amp;nbsp;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/746x480/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/841x586/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1819x904/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>TM Optimizer</title><link>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer/revision/1</link><pubDate>Mon, 21 Jan 2019 11:36:48 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4f6b610-d864-4901-9680-e39bfed9a646</guid><dc:creator>Florentina Caputa</dc:creator><comments>https://uat.community.rws.com/product-groups/trados-portfolio/rws-appstore/w/wiki/3720/tm-optimizer#comments</comments><description>Revision 1 posted to Wiki by Florentina Caputa on 1/21/2019 11:36:48 AM&lt;br /&gt;
&lt;h1&gt;TM Optimizer Help&lt;/h1&gt;
&lt;p&gt;In this section:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#usage"&gt;Using TM Optimizer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#how"&gt;How does TM Optimizer work?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="usage"&gt;Using TM Optimizer&lt;/h2&gt;
&lt;p&gt;After installation, start TM Optimizer from the Start menu under SDL-&amp;gt;TM Optimizer.&lt;/p&gt;
&lt;p&gt;On the first page of the TM Optimizer wizard, you have two choices, depending on your situation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Convert Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Optimize already converted Workbench translation memory:&lt;/strong&gt;&amp;nbsp;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.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png"&gt;&lt;img src="/resized-image/__size/813x521/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070501380v14.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png"&gt;&lt;img src="/resized-image/__size/723x463/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070522183v15.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png"&gt;&lt;img src="/resized-image/__size/746x480/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070538498v16.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png"&gt;&lt;img src="/resized-image/__size/841x586/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070554954v17.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h2 id="how"&gt;How does TM Optimizer work?&lt;/h2&gt;
&lt;h3&gt;Increases TM leverage&lt;/h3&gt;
&lt;p&gt;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&amp;#39;t spent any extra money on translations you already paid once.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png"&gt;&lt;img src="/resized-image/__size/980x199/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070583105v18.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Using the optimized TM, you see that the TM now returns a 100% match. Note that TM Optimizer only selectively removes the unnecessary tags.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h3&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png"&gt;&lt;img src="/resized-image/__size/966x175/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070602192v19.png" alt=" " /&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;h3&gt;Removes excessive formatting, e.g. font change, kerning, tracking, spacing&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Import of the TMX is much faster&lt;/h3&gt;
&lt;p&gt;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%.&lt;/p&gt;
&lt;h3 id="docx"&gt;Makes migration from DOC in TagEditor to DOCX in Studio much easier&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;Workbench Analysis Results&lt;/div&gt;
&lt;div&gt;Analysis results of a DOC test file against the original TRADOS Workbench TM:&lt;/div&gt;
&lt;br /&gt;&lt;a href="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png"&gt;&lt;img src="/resized-image/__size/1819x904/__key/communityserver-wikis-components-files/00-00-00-02-17/pastedimage1548070646395v20.png" alt=" " /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item></channel></rss>