New in version 2.20.
Weblate comes with a built-in translation memory consisting of the following:
Manually imported translation memory (see User interface).
Automatically stored translations performed in Weblate (depending on Translation memory scopes).
Automatically imported past translations.
Content in the translation memory can be applied one of two ways:
Manually, Machine translation view while translating.
For installation tips, see Weblate Translation Memory, which is turned on by default.
Translation memory scopes¶
New in version 3.2: In earlier versions translation memory could be only loaded from a file corresponding to the current imported translation memory scope.
The translation memory scopes are there to allow both privacy and sharing of translations, to suit the desired behavior.
Imported translation memory¶
Importing arbitrary translation memory data using the
command makes memory content available to all users and projects.
Per user translation memory¶
Stores all user translations automatically in the personal translation memory of each respective user.
Per project translation memory¶
All translations within a project are automatically stored in a project translation memory only available for this project.
Managing translation memory¶
New in version 3.2.
In the basic user interface you can manage per user and per project translation memories. It can be used to download, wipe or import translation memory.
Translation memory in JSON can be imported into Weblate, TMX is provided for interoperability with other tools.
There are several management commands to manipulate the translation memory content. These operate on the translation memory as whole, unfiltered by scopes (unless requested by parameters):