I’ve been beta testing the latest version of SDL Trados Studio since the summer. Four months and nine builds later, Studio 2017 has been officially unveiled and is being rolled out to the thousands of users who pre-ordered the upgrade, have a support agreement in place or are buying Studio for the very first time. What’s in store for them? Fragment recall and repair, an Advanced Display Filter, adaptive machine translation, improved segment merging and more. upLIFT fragment recall and match repair is worthy of a post of its own. So here it is.
Fragment recall: Whole TU (translation unit) match
The new upLIFT technology implemented in Studio 2017 means that a whole short segment contained in a longer one is offered through AutoSuggest. I love this because it’s almost infallible. Look at this example, where I’ve translated “capillary electrophoresis” for the first time in segment 341, and three segments later it’s offered as I type:
(Click any screenshot to open it in a separate window)
TU fragment match
Not only whole TU matches are identified, but fragments too:
In practice, this new feature more or less replaces AutoSuggest dictionaries, a static resource that has been available since 2009. Fragment Recall offers suggestions in a similar way, on the fly through Autosuggest, but it leverages TMs immediately, without having to build a dictionary. There’s no size restriction either and you get immediate context, because source and target terms are highlighted.
How to enable Fragment Recall:
Most of these options are enabled by default. But I’ll go through them one by one, in case you want to check.
Go to File>Options>Editor>Fragment Matches Window and activate the “Display results…” box:
If you don’t like the default khaki highlighting, this is also the place to choose your preferred colours:
Now, go to File>Options>AutoSuggest and activate “Fragment Matches”:
Lastly, to implement fragment matching – which is off by default – and decide on the minimum number of words (and significant words) you want returned in the fragment match window, go to File>Options> Language Pairs>All Language Pairs>TM and Automated Translation>Search and enable TU fragment.
With the above settings, fragment matches will be triggered whenever there are no results in the Translation Results window.
Experiment with the minimum word numbers. You’ll find that a very low number produces too much noise and higher numbers produce fewer results.
Impact on analysis
You may want to consider the impact of fragment matching on a file analysis. The minimum word settings are displayed in an analysis, as is the fragment word count (broken down by whole TU and TU fragment). Unfortunately, there’s no option to exclude this leverage, so watch out for ingenious fuzzy rate grids from penny-pinching agencies.
By default, the Fragment Matches window is layered under the Translation Results and Concordance windows. You may want to move it to get more vertical space for fragment results. More on this in a coming blog post.
Fuzzy Match Repair
upLIFT technology also comes into play in the new fuzzy match repair feature. Segments are repaired using a variety of resources, such as termbases, aligned translation models (see below), current TMs (whole segments and fragment recalls and even punctuation) and MT (machine translation providers).
When a fuzzy match is repaired, the match percentage remains unchanged and a spanner symbol is added. Therefore, the percentage doesn’t reflect repair work or estimated post-editing, but simply the original fuzzy value.
Some repairs need no further editing, some need light editing and others aren’t any good at all, so I just transfer the useful repairs to my translation:
The disadvantage? You can’t transfer unrepaired segments to the Editor window. Check out the last example in the screenshot above. It was perfect before the repair. What we’re missing is a shortcut to transfer a segment in an unrepaired state from the Translation Results window. I’ve added this missing feature as an idea on the SDL community forum. Please vote for it and let’s see if it’s added in a service pack.*
* I’ve now heard that this feature has indeed been slated for a future release.
How to enable Fuzzy Repair:
To make use of fragment recall and repair technology, you need to upgrade all your TMs. Whole TU unit recall is the only feature that will work without upgrading your TMs.
The upgrading process involves two steps:
- A translation model is built by performing a statistical comparison of source and target words in each segment. To make this viable, the TM must have at least 1,000 segments. SDL recommends 5,000.
- Segment fragments are identified and aligned. This step takes a long time. For example, one of my TMs with 100,000 segments took about 1.5 hours to upgrade.
Your TM will increase by up to 3 times in size because of the new fragment-aligned content. (Thanks to Helke Heino for pointing this out in the comments below.)
The good news is that the upgrade process is quite simple. Go to the Translation Memories view. Select a TM and click Settings>Fragment Alignment.
When you switch on Fragment Alignment Status, you’re warned that fragment alignment will take a long time, and then the process starts immediately, with the two steps rolled into one.
Automatic alignment after upgrading
After upgrading your TM, make sure future new segments are aligned automatically as you translate. In the same settings window, click Align new content automatically.
By enabling this box, you won’t need to repeat the alignment process ever again.
If you go back and use your upgraded TM in Studio 2015 or earlier, the TM will work correctly, but new content won’t be automatically aligned in earlier versions. In that case, align the new content manually in Studio 2017: Tick the Quick Align box (see above) and then Align Translation Units. That will align new content only and ignore previously aligned segments.
The upgrading TM process is a nuisance* and you’ll need to allot a quiet time of day or a weekend to prepare your TMs for the new upLIFT technology. But once it’s done, you’ll find fragment recall and repair is a very useful addition to your toolkit.
In a follow-up post I’ll be looking at some more new features in Studio 2017. Stay tuned!
* Stop press! Batch upgrade your TMs!
The “Reindex TMs” app on the SDL App Store has just been updated to batch upgrade a group of TMs in one go, preparing TMs for the new upLIFT technology. I haven’t tested it myself, but it sounds like a great solution. For more details and a video on this app, see Paul Filkin’s post, “More power to the elbow… upLIFT.”
Translators talk Trados
If you found this blog post useful, you might want to check out the SDL series called Translators talk Trados, where other translators look at different features and explain how they use Studio in their workflow. A great chance to learn more about Studio from colleagues!