OmegaT 3.0.6 and 3.0.7 ReviewDecember 31st, 2013, Roman Mironov
Released in November, these two versions enhance translators’ productivity with a host of useful new features:
3.0.6: Creating current translated document
Added to the Project menu, this new command makes it possible to save a translation just for the target file currently opened in the Editor pane. It comes in handy with larger projects, where you do not want to wait until OmegaT saves all the translated files. For example, the OmegaT project we use to translate this blog into Russian has over 200 files, and waiting until OmegaT creates all of them takes quite some time. With this new function, the waiting time is virtually eliminated.
3.0.6: Faster parsing of source documents
The developers optimized source document parsing, making all XML-based files load faster. The XML file formats include Microsoft Office formats, as well as XLIFF. For example, SDLXLIFF files, which are also XML-based, now load faster
3.0.6: SDLXLIFF handling improvements
The native XLIFF filter benefitted from two major improvements. The first is the ability to ignore the header tag in SDLXLIFF files, which used to make working on these files a nightmare: files would not load or would load with a lot of garbage displaying in OmegaT. This is now history. Not only is the header tag ignored, but files also load faster, thanks to the optimization I mentioned earlier.
Second, OmegaT now respects the end-of-line characters in original files. For example, if source files have CRLF (Windows EOL format), OmegaT will save them with CRLF instead of LF, which it used previously. You do not really have to understand the inner workings of this function, because everything happens without your intervention. All you need to know is that translated SDLXLIFF files that used to fail to save as target in Studio because of this issue will now save correctly.
3.0.7: Validating tags in the current file
Whereas the default tag validation command (Tools => Validate Tags or Ctrl+Shift+V) checks the entire project, this new command (Tools => Validate Tags for Current Document) checks just the document currently opened in the Editor pane. We had a project recently with large files where many tags had to be deleted. One translated file failed to save, because some tags were deleted incorrectly. When we went back to validate the tags for the entire project, OmegaT gave an overwhelming, hard-to-read list of all errors, making it difficult to pinpoint the problem. With this new command, we could have conveniently limited the list to just that one file that failed to save.
3.0.7: Match statistics per file
Available under Tools => Match Statistics per File, this report provides the same information as normal match statistics, but with a breakdown per file, similar to how Trados does it. In larger jobs, this provides more detailed statistics, allowing you to see the scope of work more clearly. Suppose the simple statistics (without analyzing against the TM) tells you there are 2,000 words in a particular file. But it does not give you any idea about whether they are all new or 95-99% matches, right? The new function allows you to see what kind of matches those 2,000 words are exactly.
Two important additions in the statistics are related to repetitions. The first line is Repetitions from other files, showing you how similar the file is to the previous files in the project. The second line, Repetitions within this file, shows the number of repetitions just within that file. Importantly, the first line has priority, meaning that OmegaT counts repetitions from other files first and repetitions within this file second.
This distinction makes splitting jobs in a team of translators team easier, showing which files are better suited for assignment. Imagine you have three files. One has mostly new words, and you assign it to translator 1. The second file has mostly new words, too, and you assign it to translator 2. The third file has many repetitions of what is in previous files. This means that assigning it to a third translator does not make sense, because translator 1 or translator 2 will have an upper hand in translating it, since the repetitions in the third file come from one of those translator’s files. You need to figure out whose file they come from and assign this third file accordingly.
3.0.7: Ctrl+F returns focus to the search field
When you click Search (Alt+S) in the Text Search window, the focus goes to the results pane, enabling you to select and copy whatever you want. But there has been no easy way to get back into the search field after running a serach, other than a mouse click. Now you can conveniently do this with the Ctrl+F shortcut.
With the addition of these new features, OmegaT has become an even more well-rounded translation program. You can download it here to try it out or join the users group to ask for support when you need help.
This is the last post this year. We wish our readers the best of luck in 2014.
Thank you for being with us in 2013.
Happy Holidays, and see you next year!