.. versionadded:: 2.20
Weblate comes with a built-in translation memory consisting of the following:
- Manually imported translation memory (see :ref:`memory-user`).
- Automatically stored translations performed in Weblate (depending on :ref:`memory-scopes`).
- Automatically imported past translations.
Content in the translation memory can be applied one of two ways:
- Manually, :ref:`machine-translation` view while translating.
- Automatically, by translating strings using :ref:`auto-translation`, or :ref:`addon-weblate.autotranslate.autotranslate` add-on.
For installation tips, see :ref:`weblate-translation-memory`, which is turned on by default.
.. versionadded:: 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.
Importing arbitrary translation memory data using the :djadmin:`import_memory` command makes memory content available to all users and projects.
Stores all user translations automatically in the personal translation memory of each respective user.
All translations within a project are automatically stored in a project translation memory only available for this project.
All translation within projects with shared translation memory turned on are stored in a shared translation memory available to all projects.
Please consider carefully whether to turn this feature on for shared Weblate installations, as it can have severe implications:
- The translations can be used by anybody else.
- This might lead to disclosing secret information.
.. versionadded:: 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.
Hint
Translation memory in JSON can be imported into Weblate, TMX is provided for interoperability with other tools.
.. seealso:: :ref:`schema-memory`
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):
- :djadmin:`dump_memory`
- Exports the memory into JSON
- :djadmin:`import_memory`
- Imports TMX or JSON files into the translation memory