Double context matches

memoQ offers context (101%) matches for:

  • the text flow: when the previous and the following segment are the same for the surrounding source segment, stored in the TM entry.
  • for ID-based context: when an associated string ID (e.g. a resource identifier in software code) is the same in the current document as in the TM entry.

    Both contexts allow the same segment to be translated in multiple different ways.

Double-context matches are 102% (or XLT) matches. You get a double-context match when the ID-based context and the text-flow context are both identical.

You get double context matches when you have running text, which can be one or more paragraphs long, and every text chunk also has an identifier coming from a content management system (CMS) or a structured document. In these cases, the text flow and the ID-based context can both be identical, and that is when you get a double context match.

101% matches if only one of the contexts match: If the translation memory can use double context, but only one type of context is identical (for example, the text flow is the same but the IDs are different), memoQ will return a single-context (101%) match. If both contexts are different, and only the segment text is identical to the text in the translation memory, the match rate will be 100% (a regular exact match).

Missing contexts count as a match: If one of the contexts are missing from both the TM and from the source text, that counts as a match. For example, if a TM match has no context ID and the source segment has no context ID either, but the text flow is the same, that will be a 102% match – if the translation memory was created with the double context setting.

memoQ's translation memories store the ID-based context and the text flow context for every segment – if they were created with the double context setting.

In structured documents (XML, Excel etc.), the text flow context is used within the structural units only: memoQ checks the text-flow context - the previous and the following segment - only inside one "structural unit". For example, if you have an Excel cell with several sentences, and a cell has a context ID assigned to it, the first segment from that cell will have an empty "previous segment" context, and the last cell will have an empty "next segment" context - regardless of any text in the neighboring cells. The neighboring cells - which have different IDs - will probably contain something entirely different and unrelated. They are not good sources of context. An XML element with a context ID is very similar: the next XML element with a different ID will probably be entirely unrelated.

Double-context matches are ranked higher than context (101%) matches. However, there is no extra match range. memoQ will count double-context matches as XLT matches, and the Statistics window will display them in the X-translated row. You also get the XLT match rate when you X-translate your document. In pre-translated segments, the translation editor shows double-context matches as XLT (102%) matches.