Each Lilt Memory has its own Translation Memory (TM) containing source/target pairs, called TM entries. Lilt improves translation speed and consistency by matching TM entries to segments that need translating.

Where TM matching is used in Lilt

  • TM segment suggestions: When working in Lilt Translate, translation suggestions are provided to linguists for the active segment. If there are any TM matches above 75%, the best match will be displayed as the suggestion. However, if there are no such TM matches, Lilt uses the associated Machine Translation model to provide suggestions to the linguist. Note that if the language pair does not have MT support, no MT suggestions will be shown.
  • Pretranslation: When Pretranslation is run, any segments that have 100% or 101% matches with TM entries in the associated Lilt Memory are translated.
  • TM Leveraging: Lilt automatically leverages TM entries in the associated Lilt Memory to populate the target text of empty, unreviewed segments with 100% or 101% matches. This is performed across all documents that share the Lilt Memory.
  • Auto-Propagation: When a linguist confirms or accepts a segment in Lilt Translate, Auto-Propagation updates matching segments (100% and 101%) with the same changes.

TM match ordering

Lilt leverages TM matches in the following order:

  1. By score. TM entries with higher match scores are prioritized over TM entries with lower match scores. For example, a TM entry that is a 100% match is prioritized over a TM entry that is a 95% match.
  2. By source: TM entries generated from a document translated in Lilt are prioritized over TM entries uploaded by file to the Lilt Memory.
  3. By recency: More recently updated TM entries are prioritized over entries that weren't updated as recently.

Note that the reviewed/unreviewed status of a TM entry does not affect match prioritization.

TM match scores

The table below outlines the various match scores in Lilt.

Match percentMatch nameMatch description
101%ICE Match (In-Context Exact Match), sometimes called a Guaranteed MatchThe 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 MatchThe selected segment has the exact same words as a TM entry.
99%99% Fuzzy MatchThe 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 MatchThe segment has similar words to a TM entry, but there are significant differences.

If the Organization Setting for 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.

How TM entries are added and removed to Lilt Memories

TM entry metadata: When a TM entry is added or modified, its metadata is updated:

  • Entry author: Email address of the author. Authorship is not always changed when an entry is updated. The sections below describe how and when authorship is updated.
  • Entry timestamp: Date and time the TM entry was last updated. The time is displayed in the viewer's time zone.

Linguist actions that update TM entries

ActionAdds
TM entry
Modifies TM entryRemoves 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.  

The last person to confirm a segment is attributed as the TM entry author.

  • When a reviewer accepts a confirmed segment without modifying the target text, the author is left as the translator who confirmed the segment.
  • When a reviewer accepts an unconfirmed segment, they are given authorship.
  • Reviews have the ability to unconfirm segments, meaning that if a reviewer unconfirms a segment and then accepts the segment, they will be given authorship.

Project manager actions that update TM entries

Action Adds
TM entry
Modifies TM entryRemoves TM entry
A project manager uploads a TM file to the Lilt Memory.  
A project manager removes a TM file from the Lilt Memory on the Manage resources page. Note: This will only remove the entries in the Lilt Memories that were added from the file.   
A project manager adds an individual TM entry in the Lilt Memory from the Manage memory page.  
A project manager modifies an individual TM entry in the Lilt Memory from the Manage memory page.  
A project manager removes an individual TM entry in the Lilt Memory from the Manage memory page.  

TM entries uploaded to the Lilt Memory by a project manager are attributed to the TM entry authors listed in the TM file.

When a project manager manually adds a TM entry on the Manage memory page, they are made the author of the entry.

When a project manager manually modifies a TM entry on the Manage memory page, authorship is not changed.

Automated processes that update TM entries

Action Adds
TM entry
Modifies TM entryRemoves TM entry
TM Leveraging populates and confirms an unconfirmed segment.  
Auto-Propagation populates and confirms an unconfirmed segment.  
Auto-Propagation overwrites a confirmed segment.  
Pretranslation populates and confirms an unconfirmed segment.  

TM Leveraging and Auto-Propagation attribute authorship to the user in the document when TM Leveraging or Auto-Propagation is run.

Pretranslation attributes authorship to either the project manager or the author of the matching entries (depending on the Pretranslation settings).