Managing Translation Memories in OmegaT

7

This post continues the series of tips on using OmegaT as a professional tool for English to Russian translation or other language combinations for that matter. Today’s focus is on the translation memory (TM) feature.

We store all translation memories in a centralized manner on a file server, which makes it easier to maintain and access the TMs. This is quite crucial in a translation company environment like ours where ongoing projects from the same end clients account for a significant portion of business. By default, OmegaT offers a project structure that keeps the “tm” subfolder in the project folder. If you need to access any additional TMs, you put them into this folder (as TMX). What this means is that you have to copy all previous project TMs to this subfolder every time you create a new project for a returning end client. You might find this inefficient, and you also face the risk of losing a few TMs along the way. You can avoid this by storing all TMs for this end client in a centralized location. If you plan to store the TMs on the same PC, this can be any folder on this PC. If you prefer to store them on a network share, you need to connect such share as a network drive (OmegaT doesn’t work well with Windows network paths starting with \). When you create your next project for this end client, change the default TM path to your centralized location path. Afterwards, you can simply copy the settings file (omegat.project) from this project to each new project. This file will always include the correct path to your centralized location.

When your project includes many 100% matches, you normally want to insert them into your translation automatically. You can’t do this from within OmegaT, because this tool currently allows inserting such matches one by one only. This may decrease your efficiency and also result in committing all these 100% matches to TM under your name, so you won’t be able to distinguish them if you need to do so (e.g. your client doesn’t pay for them and you want to skip them during editing). The workaround is to create a subfolder named “auto” in the TM folder used in this project (either local “tm” subfolder or a centralized location described above) and put the relevant TM there. When you launch the project next time, all 100% matches from this TM will appear in your translation immediately.

Whenever you create the translated files, OmegaT also creates three TMs that include all current translations, providing a few useful abilities. This TM is created in three formats: level 1 (TMX 1.1), level 2 (TMX 1.4), and OmegaT (OmegaT’s native TMX 1.1).

1. The TMX 1.4 provides a certain degree of compatibility between OmegaT and other translation environment tool (TEnT) and is, therefore, ideal when you need to provide your TM to a translation agency client who will use it in a different TEnT such as SDL Trados.

2. You may want to change segmentation or correct errors in the source text. Often, this results in two translations in the project TM, one being current (after the change) and the other being obsolete (before the change). This might be inefficient for at least two reasons: (a) when you put this TM through a spell checker or QA process, these confusing obsolete segments appear in the results; and (b) if you re-use this TM at a later time for the same end client, these obsolete translations may mislead you during translation. In such situations, the native OmegaT TM file comes in handy, because it contains current translations only. You can use it instead of the main TM (project_save.tmx). Also, if you want to remove all obsolete translations from your main TM, you can simply rename this TM file as project_save.tmx and replace the current project_save.tmx in “omegat” subfolder with this clean file.

If this blog helped you in some way, please share a link to this post on your site or through social media.

7 comments

  • It seems that you no longer have to connect a network share as a network drive for OmegaT to read files on that network share correctly. Now, OmegaT easily accesses files and folders on a network share, too.
    This means that both
    \\network share\translation memories\end client\tmx\
    \\network share\translation memories\end client\glossary\
    \\network share\translation memories\end client\glossary\glossary.txt
    AND
    Y:/translation memories\end client\tmx\
    Y:/translation memories\end client\glossary\
    Y:/translation memories\end client\glossary\glossary.txt
    will work correctly.

    Russian translation:
    Похоже, что вам больше не придется подключать сетевой ресурс как сетевой диск для OmegaT для правильного чтения файлов на сетевом ресурсе. Файлы и папки, находящиеся на совместно используемом сетевом ресурсе, для OmegaT теперь также легкодоступны.
    А это значит, что
    \\network share\translation memories\end client\tmx\
    \\network share\translation memories\end client\glossary\
    \\network share\translation memories\end client\glossary\glossary.txt
    И
    Y:/translation memories\end client\tmx\
    Y:/translation memories\end client\glossary\
    Y:/translation memories\end client\glossary\glossary.txt
    будут работать корректно.

  • Надежда says:

    Роман, а можно ли вносить правки в память машинного перевода в формате tmx? Допустим, я в процессе перевода обнаружила, что одно выражение переведено неправильно. Я могу открыть файл tmx и исправить его? Спасибо.

    • Здравствуйте, Надежда. Конечно, память TMX можно открыть и отредактировать в любом текстовом редакторе, включая блокнот Windows. OmegaT автоматически перезагрузит измененную память после перехода на другой сегмент.

  • Надежда says:

    Спасибо, Роман. У меня все получилось.

  • Plamena Tzankova says:

    Hello Roman, I was wondering if you have tried applying the centralized TM solution to the team project in OmegaT. We are testing Team Project with GIT repository and wonder if we can point each new repository project to a separate repo in which we keep centralized end client TM? I would appreciate your input. Большое Спасибо

    • Hi Plamena,

      This feature (repository mapping) is available in the current version, 4.x. I still use 3.6, though, because, based on the recent reports, 4.x still has a certain degree of risk to it—segment edits may randomly fail to commit. In 3.6, repository mapping is impossible.

      Thank you for reading the blog.

      Best wishes,
      Roman

  • Plamena Tzankova says:

    Thank you very much, for your input Roman!

Add comment