WeblateOrg / WeblateOrg/weblate

Set priority for Machine translation engines in Automatic Translation Addon.

Open
#5,770 3 comments 1 reaction 0 assignees View on GitHub
enhancement Waiting for: Demand
Dominant language
Python
Stars
6.1k
Forks
1.4k
Avg merge
9h 53m
Merged PRs (30d)
395

Description

When the Automatic Translation Addon is configured for a component multiple engines can be activated (chosen).
In the scenario skiping suggestions and translating all Messages "needing action" right away it would be great to first look them up in the local Translation Memory and in a second step, all other Messages still needing action get a translation from another engine.

Using e.G. deepl and the Weblate Translation Memory there seem to be no way to change the order or priority.
I would want to make sure the local Memory is used before the remote API is asked for a translation.
If Weblate by dedault considers local Memory at first anyway, this should be visible in the Addon's settings.

A good solution would be drag and drop capability for the list elements and some visible numbers, that indicate priority.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.