-
Type:
Improvement
-
Resolution: Unresolved
-
None
-
Affects Version/s: None
-
Component/s: InstantTranslate
-
High
-
None
-
None
-
Emptyshow more show less
Problem
Right now , when translating a single segment in the text field of InstantTranslate, newer resources will be listed higher in the result list. Even if the match rate is worse then from older resources.
Solution
Matches/translations should be listed in the order of match rate, highest first. So first all 104% from any term collection of the current client context, then all 103% etc. Down to the configured fuzzy match threshold (runtimeOptions.InstantTranslate.minMatchRateBorder), and below all those possible matches, list MT and LLM results.