If a segment has been translated, you may not see a 100% match when you open the Translation panel.

1. Translation Source > Selected Text: This setting uses the text in the actual document segment as the source text for the match.
2. Low-quality Match: As expected, this will result in a low-quality match, or no matches at all.
3. Translation Source > Source Text: This setting uses the text from the source-language document as the source text for the match.
4. High-quality Match: As expected, this will result in a high-quality match.

Given that the text in the document has been translated into German, it would make no sense if we got a high-quality match from an English translation memory. In fact, if we did see a 100% match in such a case, we should be worried about the integrity of our translation memory.

The default setting for Translation Source is Source Text. This will perform a match against the original source-language segment instead of the segment text in the target-language document.

NOTE: If no translation has yet occurred, then the text in the target-language document will be identical to the text in the source-language document. In such a case, you will see no difference between either setting for Translation Source.

1. Segments that contain special characters will not get a 100% match. This is because the one2edit™ Translation Memory (TM) stores only plain text, and not these special characters.
2. Therefore, the quality of the match will not be 100%.

Each InDesign special character has a hex value that can be detected by a regular expression. Therefore, you can adjust your segmentation rules to split these special characters into their own segments, thus ensuring a better hit rate on your TM matches.

1. The styling on this text uses an All-Caps font face, meaning even lower-case characters are displayed as upper case. The characters are not converted, however, and lower-case characters are still what is stored in the document.
2. An upper-case character has a different value to a lower-case character. In the document structure, you can see that the document source text differs in capitalization from the Translation-Memory (TM) source text.
3. The differences in the characters between the document and the TM cause a lower-quality match to occur.

A Translation Memory is case sensitive, and such styling settings can lead to lower-quality translation matches.

NOTE: Styling is not stored in the plain-text Translation Memory. Therefore, local styling (e.g. bold text) can also cause a pre-translated segment to not be marked as Done, even with a 100% text match. This is because a user is still required to apply any local styling to the correct characters in the translation.