翻訳メモリ

バージョン 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:

For installation tips, see Weblate Translation Memory, which is turned on by default.

Translation memory scopes

バージョン 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 import_memory 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.

共有翻訳メモリ

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.

Managing translation memory

User interface

バージョン 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.

参考

Weblate 翻訳メモリ概要

../_images/memory.png

管理画面

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):

dump_memory

Exports the memory into JSON

import_memory

Imports TMX or JSON files into the translation memory