Did you find this page useful? Give us feedback.
Did you find the information
on this page useful?

  Tell us more about your choice:
Missing information
Incorrect information
Misleading information
I have a question
  Enter your comment in the box below.
If you need assistance, please contact Support instead.

  Type the letters
simple PHP captcha

When you have a long source segment, and there is no hit from the translation memories, memoQ can look for smaller parts of this segment in the translation memories and term bases assigned to the project. If there are shorter segments stored in the translation memories or the term bases (along with their translations), memoQ can attempt to look for smaller parts (fragments) of your long source segment, and insert their translations into the target segment. This is done automatically: when you move to a segment, and memoQ searches the translation memories and term bases, the “patchwork” matches, or fragment matches, if there are any, will automatically appear on the hit list.

By default, the fragment matches appear on the hit list in purple color, always after the translation memory and term base matches. You can navigate to those hits just like any other TM or TB hit, then use Ctrl+Space to insert them. Alternatively, you can double-click the purple block of the hit on the list, or hold down Ctrl, and press the number (if there is one – the first 9 hits are numbered.).

Note: You can insert fragments into a segment in pressing the F4 key shortcut.


Suppose you have translated the following segments earlier:

... and you have the following entry in your term base:

Then, you need to translate the following segment in another document:

To fill in the translation for the above segment, simply place the the insertion point into the target segment. memoQ will automatically find the two smaller segments in the translation memory, and the term base entry for the term at the end of the segment. The assembled translation will automatically appear in the hit list:

To insert the suggested translation, press Ctrl+5 – or, use Ctrl and the arrow keys to navigate to the suggestion, then press Ctrl+Space.

To look for a certain part of a segment in the translation memories, select the text (or part of it), then use the Concordance or press Ctrl+K.

To look for a piece of text in the term bases, select the text, then use Look Up Term or press Ctrl+P.

Pre-translation with fragment assembly

You can also use fragment assembly during pre-translation (choose Pre-Translate on the Preparation ribbon tab). When asking memoQ to pre-translate a project, document or the selected segments, memoQ will attempt to put translations together from fragments if there is no translation memory hit for a particular segment:

By default, memoQ will automatically perform fragment searching during pre-translation. To disable automatic fragment searching, clear the Perform fragment assembling check box in the Pre-translate and statistics dialog.

When you click the Settings... link, the Fragment assembly settings appear. Here you can configure the matches to include in the fragment assembly: Terms, Non-translatables, Numbers, Auto-translatables, Fragments from TMs and corpora. Check the check boxes of the matches which you want to include.

In the Suggest only section of this dialog, you can choose from 3 options of coverage:

Full matches covered by one single hit: Choose this option to get only full matches with one single hit in the pre-translation with using Fragment assembly.

Full matches covered by several hits: Choose this option to get full matches which have several hits in the pre-translation with using Fragment assembly.

Matches with a coverage of at least: Choose from the drop-down list the percentage for the match coverage. By default, it is set to 50%, i.e. when at least the match is covered 50%.

Check the Delete source text without any match check box when you do not want to have the source text inserted during pre-translation.

Check the Do not change the case of terms check box to not automatically change the upper/lower case of terms. For example: you have  the word Cancel in the source text, cancel in the TB as source, and in the TB  you have abbrechen as target for it, then memoQ will not change it to Abbrechen. Terms will always be left in the form they are coming from the term base if you check this check box - even at the beginning of the segment.

Fragment assembly mechanism

When attempting to put together a translation from translations of fragments, memoQ will always look for the longest possible fragment from the beginning of the segment. When a fragment is found, memoQ will look for the longest possible fragment again from the point where the previous fragment ended. If it does not find a fragment from the beginning of the segment (or the point it is searching from), it will attempt to look for a fragment from the beginning of the next word. If the subsequent searches are also unsuccessful, memoQ will move from one word to the next until a fragment is found or the end of the segment is reached.

In fragment searching, memoQ searches the translation memories and the term bases in the project. When searching translation memories, memoQ uses exact translation memory matches only. It does not attempt to find approximate (fuzzy) matches for the fragments in the translation memories. When searching term bases, memoQ does not use prefix matching.

When putting together a translation from fragments, memoQ will always cover the entire source segment. When looking for fragments, memoQ always goes word by word. If a word is not covered by a fragment match – that is, memoQ had to skip a word and continue searching from the next one –, the gap will be filled in by inserting that word in the source language. See the example above: some English text still remains in the suggestion. This is because memoQ did not find TM or TB entries that would cover those words.

When memoQ has to choose from multiple term base hits

Most of the time, fragment assembly will replace terms in the source text. When there are two or more term base hits for the same source-language words, memoQ has to choose one. For this reason, memoQ will score the term base hits, and the one with the highest score wins.

Of course, the longer hit is always stronger, but when the two or more hits are equally long, memoQ needs to look at them in more detail.

On the one hand, you can set up priorities between term bases - if a term comes from a more important term base, it will win.

On the other hand, If they come from the same term base, memoQ still needs a way to decide.

This process works if ranking is turned on. To turn on ranking, open the Hit list filter settings dialog, and check the Order term base hits primarily by rank and metadata check box.

Then memoQ will check how much a term base hit has in common with the project. If one term base hit has two details that match the project, and another has three, the hit that has three details will win.

If both term base hits have the same number of details that match the project, memoQ will check how important these details are. The order of importance, from most important to least important, is the following:

Project name

Client name



For example, if one term base hit has a matching client name field, and another has the same subject, the first one will win because the client name is more important than the subject.