TM Leverage tool

The TM Leverage tool queries a translation memory (TM) for each block's source text and pre-fills the target with the best match. It tries an exact match first, then a fuzzy match above a configurable threshold, recording the match score and type (exact or fuzzy) on the block. It requires a target language and a TM provider; without a TM the tool has nothing to leverage.

Whether a match is written into the target is governed by a fill threshold and an "only if empty" option, so high-confidence matches can be applied while weaker ones are recorded but left for review. A no-query threshold lets the tool skip the TM lookup when an existing candidate already scores high enough. Optionally, all leveraged matches can be written to a TMX file.

IDtm-leverage

SourceBuilt-in

Categorytranslation

Cardinalitybilingual

Requirestarget-language, tm

Tagstranslation

Parameters

Parameter	Type	Default	Description
`downgradeIdenticalBestMatches`	boolean	false	Reduce score by 1%% when multiple identical exact matches are returned
`fillIfTargetIsEmpty`	boolean	false	Fill the target only when it has no existing content
`fillTarget`	boolean	true	Copy the best translation candidate into the target content
`fillTargetThreshold`	integer	95	Minimum match score required to fill the target
`fuzzyThreshold`	integer	70	Minimum score for fuzzy matches (0-100)
`makeTmx`	boolean	false	Create a TMX file with all leveraged matches
`noQueryThreshold`	integer	101	Skip TM query if existing candidate scores at or above this value (101 = always query)
`tmxPath`	string		File path for the generated TMX document

Configure these parameters interactively and copy the flow-step YAML on the Tool Reference.

Examples

Apply only high-confidence matches

Fill the target from matches scoring 95 or above.

fillTarget: true
fillTargetThreshold: 95

Leverage and export to TMX

Lower the fuzzy threshold and write matches to a TMX file.

fuzzyThreshold: 60
makeTmx: true
tmxPath: ./leverage.tmx

Processing notes

Operates on translatable blocks with a non-empty source; other parts pass through unchanged.
Exact matches are tried before fuzzy matches; the match score and type are recorded as block properties.
With a structure-aware TM provider, matching runs against the block's inline-code structure and fills carry the matched entry's runs, so markup placeholders survive the fill; a 100% match means text and structure agree.
Ambiguous matches (several full-score entries with differing targets) are recorded but never fill the target — the choice surfaces for review instead of being picked by storage order.

Limitations

Requires a target language and a TM provider; with no TM there is nothing to leverage.

← Back to the Tool Reference