Prioritization order | Prioritization method | Prioritization |
---|---|---|
1 | Match percent | TM entries with higher match percents are prioritized over TM entries with lower match percents. For example, a TM entry that is a 100% match is prioritized over a TM entry that is a 95% match. |
2 | Recency | More recently updated TM entries are prioritized over entries that weren’t updated as recently based on the TM entry’s modification time. |
Prioritize recency setting
Match percent | Match name | Match description |
---|---|---|
101% | ICE Match (In-Context Exact Match), sometimes called a Guaranteed Match | The selected segment has the exact same words as a TM entry. In addition, the segments before and after the selected segment are also identical to a set of three consecutive segments in the TM. |
100% | Exact Match | The selected segment has the exact same words as a TM entry. |
99% | 99% Fuzzy Match | The selected segment is almost exactly the same as a TM entry. A 99% match usually indicates there is a whitespace or tag mismatch. |
>75% | Fuzzy Match | The segment has similar words to a TM entry, but there are significant differences. |
Case-sensitive matching
is enabled, TM match scoring takes into account any differences in letter casing; otherwise, casing is ignored.
In LILT, 100% matches that have whitespace differences or tag differences are downgraded to 99% matches. In the example below, the bottom segment doesn’t have a new line whitespace like the top segment does, so the TM match for the bottom segment is displayed as a 99% match.
The hares and the tortoise
The hare and the tortoise
> La liebre y la tortuga
The hare<sup>hares</sup> and the tortoise
. The TM entry uses hare
, while the source uses hares
. Any words in the TM suggestion that are missing from the source are underlined. Substitutions from the source are displayed in superscript.
Escape
to close it. Once closed, you can still access and use the TM suggestion, but the TM diff display (including match percent) will go away. The diff display can be brought back by refreshing the page.
Segment context
pane displays TM matches sorted in the following order:
Segment context
pane is not the same as the TM match order. While the Segment context
pane sorts by reviewed/unreviewed status, TM matching ignores reviewed/unreviewed status.
Segment context
pane will display so. Click the identical results
dropdown to display the following metadata for each identical TM entry:
Action | Adds TM entry | Modifies TM entry | Removes TM entry |
---|---|---|---|
A translator confirms a segment. | ✓ | ||
A translator modifies and confirms a segment. | ✓ | ||
A translator unconfirms a segment. | ✓ | ||
A reviewer accepts a confirmed segment. | — | — | — |
A reviewer modifies and accepts a confirmed segment. | ✓ | ||
A reviewer accepts an unconfirmed segment. | ✓ |
Action | Adds TM entry | Modifies TM entry | Removes TM entry |
---|---|---|---|
A project manager uploads a TM file to the Data Source. | ✓ | ||
A project manager removes a TM file from the Data Source on the Manage resources page. Note: This will only remove the entries in the Data Source that were added from the file. | ✓ | ||
A project manager adds an individual TM entry in the Data Source from the Manage entries page. | ✓ | ||
A project manager modifies an individual TM entry in the Data Source from the Manage entries page. | ✓ | ||
A project manager removes an individual TM entry in the Data Source from the Manage entries page. | ✓ |
Manage entries
page, they are made the author of the entry.
When a project manager manually modifies a TM entry on the Manage entries
page, authorship is not changed.
Action | Adds TM entry | Modifies TM entry | Removes TM entry |
---|---|---|---|
TM Leveraging populates and confirms an unconfirmed segment. | ✓ | ||
Overwrite Confirmed Segments populates and confirms an unconfirmed segment. | ✓ | ||
Overwrite Confirmed Segments overwrites a confirmed segment. | ✓ | ||
Pretranslation populates and confirms an unconfirmed segment. | ✓ |