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

You can rank term bases to give priority on the hits in the translation results pane. You can set the priority of a term base in ranking it higher or lower. This can come in handy when you want to maintain one term base for various jobs, but different clients need the same term translated differently. And then you want the terms that are more relevant to appear before the others.

You may also have a huge TM for a client in which you or the LSP you work for has diligently tagged segments with metadata. When translating for that client, you want to see all matches, but the matches having the same properties as the project should appear before the others in the Translation Results pane. Especially when there are several 100% matches – translators tend to not look for further 100% matches.

Prioritize entries with different metadata in the same term base or Translation Memory. In projects, you can store project, client, subject and domain, and when you filled in these fields, then memoQ compares the TB entry metadata against the project metadata when showing the order of results in the translation results pane. Prioritized matches also come first in Predictive Typing, AutoPick and Fragment Assembly.

For TBs, the metadata are project, client, subject and domain, in this order. An entry is getting priority if all four metadata are identical to that of the project – then if three, two, one are/is identical. If there are two TBs, and for one the identical metadata entries are project and domain, and for the other client and subject, the one with project wins because project is more important than client. If one has client and subject, the other has client and domain, the first one wins because subject is more important than domain.

For Predictive Typing/AutoPick, the first items to be offered are the ones that get priority, like in the Translation Results pane. For fragment assembly, the first item gets inserted.

The matching entries for the same term appear in the Translation Results pane, predictive typing lists and AutoPick lists in their order of priority, which will be determined by

1.whatever you determined in the hit list filter settings

2.number of identical metadata: the metadata of the term base entry (not the term base itself) is compared to the metadata of the project.

3.importance of metadata: memoQ uses an internal counting mechanism to determine higher priority (the project field for instance gets a higher point value than client, subject and domain).


See also:
Hit list filter settings

TM settings