GET A FREE CONSULTATION OR SAMPLE TO GET YOUR PROJECT GOING.

Yes, I want my consultaion

Video: Translation Memory-Related Changes in OmegaT 3.1.0

This video focuses on improvements introduced in the latest release of OmegaT with regard to translation memory.

Mark Auto-Populated Segments

Mark Auto-Populated Segments in OmegaT

Available under the View menu, this option provides a visual way to recognize matches inserted from translation memories. To see how it works, add a TM with 100% matches either to the auto or enforce subfolders in the TM folder of your project. When you open the project, the 100% matches get populated and their background color changes. As soon as you edit an auto-populated segment, the color disappears. Note that colors may combine: for example, throwing in the Mark Translated Segments option results in a mixed color that might be confusing.

This function is designed to make distinguishing between 100% matches and other text easier. This new visual way is a better alternative to opening a segment and looking into the Fuzzy Matches pane to find out whether it is a 100% match.

Enforce folder for overriding project_save.tmx

Enforce folder in OmegaT
Suppose you get disconnected from the SVN server while working on a team project and then work offline. How do you make sure your translations make it to the server after going back online? New translations are not an issue, since you can insert them from the auto folder. But what about those translations that you edited? The auto folder can only add new translations, but it does not overwrite those already in the project_save.tmx. However, the newly added enforce folder will. It instructs OmegaT to override all segments with those found in the TMXs within this folder.

Registering segments with identical source and target

Registering segments with identical source and target in OmegaT
Previously, any segments where source and target were identical made it to a project’s translation memory only as long as Allow source to be equal to target was enabled under Editing Behavior. However, using this option may be suboptimal, because it forces OmegaT to save to the TM every segment that you open, regardless of whether you touched the text at all. Among other things, this leads to confusing statistics: segments that are not really translated erroneously appear as if they were, in the statistics. Now you can avoid writing untranslated segments to the TM. This is achieved by disabling the Allow source to be equal to target option first and then using Register Identical Segment (Ctrl+Shift+F) under the Edit menu to save segments with identical source and target to the memory manually.

If you found this video helpful, please tell us so by “liking” us on Facebook. More information about OmegaT is available by clicking the links below.

8 comments

  • Kos Ivantsov says:

    Enforce functionality is great, but it’s worth remembering that if a TMX file resides in /tm/enforce folder, and in the meantime segments that have been inserted from the enforced memory were edited, all the edits will be gone at the next project reload when memory enforcement is activated again.
    I find that the best way to use enforced memories is to put them into /tm/enforce, reload the project, and remove them from the folder right away, unless I want some immutable segments in the project.
    But if there really are “canonized” translations in the project, and they are to stay the way they are no matter who edits them, it can be achieved with /tm/enforce as well. Though it’s hard to think of a project with such a requirement.

  • Didier Briel says:

    >Though it’s hard to think of a project with such a requirement.

    This was developed precisely for such a user. The context is software localisation, where terms from the program cannot be changed.

    Didier

    • Manuel Souto Pico says:

      >Though it’s hard to think of a project with such a requirement.

      It is the case also in projects I’m involved with. There’s a negotation process and then some translations are approved. After that, they cannot be changed, so the “enforcing” feature is perfect.

  • Manuel Souto Pico says:

    Very interesting! One question, though: Why do I not have a Folders menu?

  • agen bola says:

    I was just seeking this info for some time. After 6 hours of continuous Googleing, at last I got it in your site. I wonder what’s the lack of Google strategy that don’t rank this kind of informative sites in top of the list. Normally the top websites are full of garbage.

Add comment


About the Author

Roman Mironov
Roman Mironov
CEO & Founder

As the founder of Velior, Roman has had the privilege of being able to turn his passion for languages into a business. He has over 15 years of experience in the translation industry. Roman has helped dozens of clients increase sales by making their products appealing for speakers of other languages.