Did you know that with the release of the version 3.0, OmegaT has become easier to use than ever?
Watch this video to see some of the most important changes in OmegaT 3.0 that bring usability to the next level:
- OmegaT now comes with the tokenizers. The tokenizers are stemmers that allow OmegaT to treat words with the same stem such as “improvement” and “improve” as similar words for the purpose of the glossary and fuzzy matching. Until this last version, they were available as a plugin only. To use a tokenizer, a user had to download a plugin, put it into the plugins subfolder, and create a BAT script that launched OmegaT with the appropriate tokenizer. If you translated from different languages, you had to have a separate script for each source language. This could be quite challenging for non-technical folks. Well, this is history. Because the tokenizers are now integrated in OmegaT, they load automatically based on the source and target language settings of your project. You can check the tokenizer used in the Project Properties dialog. In this example, an English tokenizer enables OmegaT to match the noun “improvement” in the glossary to the verb “improve” in the source text.
- A similar improvement is integration of the Language Tool plugin. While this plugin wasn’t as difficult to manage as the tokenizer plugin, you still had to take a few additional steps before making it work for you. OmegaT 3.0 eliminates all those steps. Just go to Options and enable Language Checker. In this segment, Language Tool detects two problems. The sentence starts with a lower-case letter. And there’s a double space. Before using the new version, make sure you delete the two plugins, tokenizers and LanguageTool, from the plugins folder if you have them.
- A frustrating behavior with the versions until 3.0 was the removal of all tags from the beginning and the end of the segments. While this function is indeed practical in most cases because it removes superfluous tags, it also occasionally removes some of the tags that you need in the target segment to write the translation correctly. In this example, this function deletes a variable tag, which must be kept in the translation because I’ll need to move it to a different place in the translation. I can open the source file with a text editor to confirm there’s a variable tag. It represents the name of a test. The actual text looks like this. I want to translate this sentence into Russian, which normally has a different word order, i.e. “strip of CSF” rather than “CSF strip.” With the tag outside of the segment, there’s absolutely no way for me to put the word “strip” in front of “CSF” in the translation. With the release of the version 3.0, however, this is no longer a problem. I just go to the filter settings—whether global or project-specific—and disable the Remove leading and trailing tags checkbox. After reloading the project, OmegaT displays the tag, enabling me to move it around freely in a segment.
- The file filters dialog now also includes two other options. I haven’t used them yet. You may want to discover them on your own.
That’s it for today. Thank you for your time. Stay tuned for other materials about the excellent progress of OmegaT. You may also want to watch my first video about OmegaT 3.0 that covered tag-related improvements.