How to use the fragment assembly
Description: This article describes how the fragment assembly feature works.
The fragment assembly is a function of memoQ that automatically puts together a complete segment suggestion based on the source segment and the matches in the source segment.
The suggestion segment is assembled from the following elements, in this order of priority:
- term base hits,
- non-translatable hits,
- number hits,
- auto-translatable hits,
- fragment hits coming from the translation memory.
- The parts of the segment where no match was found are filled in from the original source segment or are completely omitted, according to the settings.
Fragment assembly settings
The fragment assembly settings are available from the My memoQ > Options > Advanced lookup setting > Fragment assembly tab.
The settings can also be changed when you start pre-translation from Preparation > Pre-Translation, check the Perform fragment assembly checkbox, and then click on the Settings command link.
The settings window looks like this:
You can choose what kind of hits you want to include into the fragment assembly. The hits are listed in the order of priority, which means that if there are several matches for a source segment part (eg. auto-translatable and number hit for a number), then the fragment assembly will use the one that has higher priority.
If you uncheck all the checkboxes that means that fragment assembled hits will not be offered when you translate.
You can also set the required coverage level for your source segment. The options are:
Full matches covered by one single hit - Fragment assembly will only offer a match, if the whole source segment is covered by one match. This means that the coverage has to be 100%. For example if the source segment is a number, or a term from the term base, or the part of a translation memory match. Otherwise no fragment assembly match will appear in the translation results pane (purple).
Full matches covered by several hits - The fragment assembly will offer a match if the whole source segment is covered by one or several matches. This means that the coverage needs to be 100%, otherwise no fragment assembly match will be offered.
Matches with a coverage of at least... - You can set the minimum coverage for the source segment. The minimum coverage means that at least this proportion of the source segment needs to have a match.
Let’s assume that you have 1 term in your TB: apple – Apfel
Your source segment is: Apples and pears. (14 characters, spaces and punctuation don’t count)
There will be one hit: apple, which covers Apples, which is 23.3% of the segment. If you set the minimum coverage to for example 50%, the assembled fragment will not be offered, but if you set it to 23% or less, the assembled fragment will be: Apfel and pears.
There is one more option: you can exclude parts of the source segment from your offered match. Using the previous example the offered suggestion without source parts would be: Apfel
Other factors influencing the fragment assembly
The settings in Translation > Automatic lookup and insertion are still there..., but the threshold you can set there for minimum coverage (Nr. 3.) only has an effect on the fragment assembly match if the coverage at the previously mentioned settings window is higher than the threshold here. The reason for this is that if you set the coverage requirement high in the fragment assembly settings window, and the match coverage does not reach that level, then the suggestion is not even created.
Please sign in to leave a comment.