...
Cross-file repetitions are just those segments which are repetitions of the first instance of a particular segment (they have the same content) of the first instance of a certain segment that . This segment is placed in the primary file (the file in which a given particular segment occurs for the first time). In other words, if you have segments in other files with that are repetitions of a certain particular segment from the primary file, those are called cross-file repetitions.
The analysis of a project takes place in a "top-to-bottom" fashion. When you create a project with multiple files that have the same segment, the first instance of it that segment will be marked as Unmatched. Other instances of that segment in other files will be marked as a Repetition with the this information: Repeat - matched across files:
...
If you such see this information, it just means that this segment was has not been translated yet in any file.
If any instance of that segment in any file is translated , then other occurrences will receive the relevant translation will be inserted in other occurrences if you access them in XTM Workbench, in the "Edit" mode:
...
| Info |
|---|
Repetitions and cross-file repetitions are two separate functionalities. The repetitions update is based on the user's settings in XTM Workbench. The cross-file repetitions, however, are subject to the normal update updating of matches, i.e. the current segment + 2 segments below will be updated. |
If a given particular cross-file repetition receives a TM match upon the project analysis, its first instance will have a ICE/Leveraged status whereas the instances in subsequent files will receive be assigned Leveraged status , and as such they will be displayed in Project Metrics (external matches always take precedence over any kind of internal matching). This is caused by the fact, that the first instance was not marked as a repetition during the analysis of when the file was analyzed:
...
Although there cannot be a match from the same segment where when it has been translated without reanalysis, it is expected that the first occurrence can receive matching a match from the other segment, which in this case , is the child repetition.
Will
...
a segment like this, which is matched to another file that has been removed from the project, be counted as a Fuzzy Match or as a No
...
Match?
That depends which file will be is removed. If you have two files in a project - , one with an unmatched segment and the second one with information: Repeat - matched across files, and you delete the file where in which the segment is unmatched, the second file will unfortunately have a false contain an incorrect repetition unless you re-analyze reanalyze the whole entire project. In general, when files are added/deleted after the project creation, a full project re-analysis reanalysis is required in order to calculate cross-file repetitions properly.
...
The "Hide repeated segments" option
XTM allows for enabling In XTM Cloud, you can enable the option to hide repeated segments, and this also applies to cross-file repetitions (of course, except for the first instance of the segment). The said This setting can be enabled in Configuration -> → Settings -> → Translation -> → TM -> → Repeats:
...
Once enabled, the option is activated in the "create a new project" form when you can specify the percentage of a given particular file that at which repetitions occupy, at which the option shall be activated:
...
Good to know!
PleaseRemember that, remember that while repeated segments in XTM Workbench can be hidden, they are automatically populated with the newest translation in subsequent files , thus so they will be translated accordingly in a target file once the latter that file is re- generated again. Also, the Metrics will still display those repetitions, and the file concerned will show the original number of segments in the Project editor -> → Workflow section.