SDL Studio: Fragment Matching against Whole Translation Units (Christine Bruckner)


  • Administrator
  • Hero Member
  • *****
    • Posts: 811689
    • Gender:Male
  • point d’amour
Fragment Matching against Whole Translation Units (TUs)

SDL Trados Studio 2017 introduced fragment matching. During TM lookup, fragment matching now also retrieves and displays smaller chunks such as

— whole translation units
— fragments of translation units

Option a), matching against whole translation units (TUs), means that complete translation units with a default minimum length of two words contained in the TM will be automatically found within longer new segments and displayed in the Fragment Matches window and via AutoSuggest.For example, if you translate a software manual and have the already translated (shorter) software strings stored in one of your TMs, you will see the software strings referenced in sentences as fragment matches even if they are too short to be recognized as fuzzy matches.   

While I am a bit skeptical about the usefulness of retrieving and displaying auto-aligned TU fragments at the sub-segment level (option b), displaying whole translation units (TUs) can often be really helpful and avoid (some) manual concordance searches.

However, the Fragment Matches window is only displayed in the foreground when there are no results available in the Translation Results window -- so useful whole TU matches could be hidden by 100% or fuzzy matches from your TM or by MT proposals. To avoid this, undock the Fragment Matches window from its position next to the Translation Results tab and move it to a separate window position so that it will be always visible in the Studio editor:

(If you do not manage to set up the Fragment Matches window as shown above -- don't worry: You can return to the previous layout at any time via the Reset Window Layout button in the View ribbon.)

Moreover, whole TU matches can be a valuable source for terminology: You can easily mark them in the Fragment Matches window and send them as terms to your MultiTerm termbase.

You might also want to do it the other way round: Convert a large termbase like the Microsoft Terminology into a reference TM in order to make it available for whole TU fragment matching. You can do this via the Glossary Converter or the Bilingual Excel file type.

When you run a Studio analysis, you can see the number of whole TU matches in the corresponding Fragment Words (whole TU) column of the analysis report, so you might get a feeling for how much you could benefit from such fragment matches during your translation.

See also:

« Last Edit: 07 Sep, 2019, 10:00:11 by spiros »


Search Tools