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

Yes, I want my consultaion

OmegaT 3.0 Review, Part 3: Search and Navigation Improvements

Have you noticed that OmegaT 3.0 includes many new features, but you’re still not sure how to put them to use?

Watch this video to get a grasp of some of the new features, including the changes in the Text Search dialog and within the Editor:

Script:

  1. The Text Search dialog has been revamped. The Search in Files section now displays at the top. I can select between searching in the project or in the files. This is more intuitive than ever before.
  2. When I search in a project, I now have three general options. The new Memory checkbox enables me to search just in the source files and the project’s translation memory, i.e. the project_save.tmx. This search result comes just from the source file.
  3. The TMs checkbox has the same function as in the previous versions. The only thing that changed is that it’s been moved to this new section. These search results come just from the translation memory in the tm subfolder of the project.
  4. The Glossaries checkbox is a completely new function that allows me to search in the glossaries as well. First of all, adding the glossary into a search mix gives me a bigger picture of what’s happening in the project. For example, when the glossary and the TM have different translations for a term, I can notice this immediately and choose the correct one while previously, I would see only one version of the translation. The new search is also very helpful with larger glossaries such as the Microsoft glossary. When I search in it through the Text Search dialog, I get much more useful results than the Glossary pane might provide.
  5. If I want to get the results from all the three sources, I can enable all the three checkboxes.
  6. When I select searching in the files, the other options are conveniently grayed out. This option enables me to browse to a folder and search within the files in that folder. For example, this search result comes from a file located in that folder.
  7. Another new option here is the Translated checkbox. As the name implies, this search returns the results only from those segments that are already in the project’s translation memory. For example, when I search for “CMS” with this checkbox disabled, I get the search results from all the segments—whether translated or untranslated. But when I enable this checkbox, I get just one result—from the only translated segment. If I repeat the search with this checkbox disabled, I can see that these three segments do not have any translations yet, which is the reason is why they don’t come up in the search results.

That’s it for the search options. Let’s take a look at a few improvements related to the Editor pane.

  1. I can move to the next untranslated segment by selecting Next Untranslated Segment under the Go To menu or pressing Ctrl+U. But what if I want to move to the next translated segment? In this example, I have a lot of untranslated segments in the project that I want to skip because these numbers don’t require translation. Now I can do this with a convenient function called Next Translated Segment under the Go To menu or the Ctrl+Shift+U shortcut.
  2. It’s easier to select the matches in the Fuzzy matches pane now because the shortcut became more intuitive. While previously, I could only press Ctrl + the number of the match, e.g. Ctrl+1, Ctrl+2, or Ctrl+3, I can now also press Ctrl + arrow up or down to switch between the matches. And when I’m done selecting, I can insert the match into the target segment with another shortcut.
  3. If I want to use a machine translation output on a per-project basis rather on a per-segment basis, I can create a TMX with the MT output. The latest version of OmegaT can let me know me whenever I insert a match that comes from this TMX. To do so, I need to put the respective TMX into a subfolder named “mt” in the translation memory folder. When I insert an MT match, the background of the active segment changes to red. As soon as I edit this segment, the background color becomes normal. If I simply leave the segment and then return, the background is removed as well.

Alright, with the three video reviews of OmegaT 3.0, I’ve covered almost all of the improvements. If you missed any of the previous videos, here is the link to the video about tag-related improvements and the video about usability enhancements.

If you’re already using the latest version, make sure to share your experiences or ask questions in the comments. Thank you.

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.