Documentation Center

Trados repetitions and cross-file repetitions

Consult this topic to learn more about how repetitions and cross-file repetitions are calculated.

What are repetitions and cross-file repetitions?

Repetitions refer to fuzzy matches or 0% matches which appear more than once in the same file. Segments which are 100% matches, Context Matches, or PerfectMatches are not counted as repetitions, even if they occur several times within the same file.

Cross-file repetitions refer to fuzzy matches or 0% matches which appear more than once across several files in a project. Segments which are 100% matches, Context Matches, or PerfectMatches are not counted as cross-file repetitions, even if they occur several times within the same project.

Where can repetitions and cross-file repetitions be consulted?

Repetitions and cross-file repetitions can be consulted in the task statistics, in the Analysis Statistics report, and in either Trados Studio or Trados Online Editor. Repetitions and cross-file repetitions are not counted as a separate category in the task confirmation statistics.

What influences the way in which repetitions and cross-file repetitions are calculated?

The order in which files are processed by the system determines whether the repeated segments are counted as repetitions proper or as cross-file repetitions. If a project includes more than one file which needs to be translated, the first processed file will count only repetitions, while all subsequently processed files will count both repetitions and cross-file repetitions.

Use case 1: Repetitions and cross-file repetitions in projects with one file

The file contains a total of 58 segments, namely 50 new unique segments and 8 identical segments. The 8 identical segments are distributed as follows:
  • One 75%-match segment occurring 2 times: The machine works as expected.
  • One 85%-match segment occurring 2 times: Several restrictions apply.
  • One 100%-match segment occurring 2 times: Open the frontal hatch.
  • One PerfectMatch segment occurring 2 times: Remove the debris.

The 100%-match segments and the PerfectMatch segments are counted separately in their respective categories.

The first occurrence of each non-unique fuzzy match (75% and 85%) is counted in the respective categories (75-84% and 85-99%). All subsequent occurrences of each non-unique fuzzy match (75% and 85%) are counted in the Repetitions category.

Here is how the segments are distributed behind the scenes:
New75-84%85-99%100%PerfectMatch
501122
Repetitions01100
Cross-file repetitions00000
Total502222
Total no. of segments58

Use case 2: Repetitions and cross-file repetitions in projects with multiple files

The project contains 2 files, called File1 and File2. File1 is processed first.

File2 contains a total of 13 segments, namely 5 new unique segments and 8 identical segments. The 8 identical segments are distributed as follows:
  • One 75%-match segment occurring 2 times: The machine works as expected.
  • One 85%-match segment occurring 2 times: Several restrictions apply.
  • One 100%-match segment occurring 2 times: Open the frontal hatch.
  • One PerfectMatch segment occurring 2 times: Remove the debris.

The 100%-match segments and the PerfectMatch segments found in File2 are also present in File1, but they are counted separately in their respective categories in File2.

The 75%-match segment found in File2 is not present in File1. Therefore, the first occurrence of The machine works as expected is counted in the 75-84% category, while the second occurrence of the same segment is counted in the Repetitions category.

The 85%-match segment found in File2 is also present in File1. All occurrences of Several restrictions apply are counted in the Cross-file Repetitions category.

Here is how the segments are distributed behind the scenes for File2:
New75-84%85-99%100%PerfectMatch
51022
Repetitions01000
Cross-file repetitions00200
Total52222
Total no. of segments13