There are numerous ways of doing this, and OmegaT leaves it very much up to you, the user, how you go about it. Methods of managing translation memories when using OmegaTĪs described above, OmegaT has, at the time of writing (November 2020), no functions of its own for managing translation memories you must manage them yourself in your file manager. If you are not sure whether OmegaT has loaded an input TM, a simple way of checking is to search (with Ctrl-f) for a word or phrase that you know to be in it. Individual segments in input TMs are displayed to you when a segment identical or similar to the active segment (full match or fuzzy match) is found. Instead, if they have been placed in the \tm\ folder, they are loaded automatically by OmegaT when the project is opened. OmegaT does not have a function with which the user can open input translation memory files directly. Viewing the content of translation memories in an OmegaT project For more details of the differences between the three variants of output translation memories, refer to the OmegaT manual. The text contained in these three files is identical they differ only in the amount of formatting information they also contain. They are all placed in the project's main ("root") folder, and have the names -level1.tmx, -level2.tmx and -omegat.tmx. Three output translation memory files are created when you hit Ctrl-d. (OmegaT does enable you to call up your file manager and a particular project within your folder with Project > Access Project Contents.) They are deposited in the project's root folder, and what you then do with them is left to you. Here we have an idiosyncrasy of OmegaT: there is no function within OmegaT itself for copying, moving or exporting output translation memories to a chosen location. You can use this output TM as an input TM in future projects. It also creates an output translation memory of the project. a translation in a Word file, if your source text was also a Word file) to be created. Hitting Ctrl-d in OmegaT causes your translated documents (e.g. You may however want to limit the number (in the interests of speed), and select them carefully, in order to have more relevant matches displayed to you. individual TMX files) you can have in a project. There is no limit to the number of input translation memories (i.e. Once you have selected a different translation memory folder, OmegaT regards it as being part of the project. Selecting a translation memory folder in this way instructs OmegaT to look for the input translation memories there instead of in the default location of \tm\. However, if you have a folder on your computer in which you have collected translation memories, you can make this folder the project's translation memory folder by selecting in it OmegaT using Project > Properties, then hitting the Browse button next to Translation Memory Folder. In order for OmegaT to make use of them, place them in the project's \tm\ folder before loading the project (or, if the project is already loaded, re-load it again).Īs standard, the project's translation memory folder is at \tm\ (where is the project's main or "root" folder). Input translation memories are translation memories created from past translations that are to be used in the active project for reference. The internal project translation memory is used by the OmegaT program and as the user, you do not normally need to deal with it. It is therefore empty when the project is first created. This file contains only the segments that have been translated in the project up to now. It is the file project_save.tmx and can be found in the project's \omegat\ folder. The internal translation memory is the project's own TM, which remains within the project, i.e. Each project has internal, input and output translation memories. It recognizes translation memories only in the context of a project. The OmegaT program does not have its "own" translation memory. Understanding this concept is crucial if you aim to use OmegaT effectively. In this HowTo, "a translation memory" therefore refers to a file. OmegaT stores translation memories in the industry-standard TMX file format. A segment is usually a sentence, though it may be just a phrase, or in some cases may span several sentences or even a whole paragraph. Each translation unit consists of a pair of segments: the segment in the original text, and the segment in the translation. A translation memory ("TM") is a database in which texts are broken down into segments and stored in "translation units".
0 kommentar(er)
