In my latest webinar, I looked at three important scripts that you can use in OmegaT. Watch this video to learn how to use them.
Written by Piotr Kulik and called spellcheck.groovy, this script makes it possible to check spelling in the entire project, thus complementing spell checking that happens on-the-fly in the Editor pane. After you run the script, you get a list of potential errors that you can ignore (write to the project’s ignored_words.txt file) or learn (write to the project’s learned_words.txt file). Normally, you want to “learn,” i.e., add to your custom dictionary, those words that are actually correct. By reusing this custom dictionary across projects (large learned_words.txt file), those words will no longer come up as errors in future projects. And you want to “ignore” those errors that are no good for your dictionary, because in a different context, they might be errors. For example, an English abbreviation such as “ISE” in an English to Russian translation is fine as long as it is untranslated as an abbreviation. However, when this is a part of the English word “RISE” that the translator forgot to delete, the spell checker should detect it. But if you add “ISE” to the dictionary, the spell checker will ignore it whether it is correct or not.
To make running spell checking more intuitive, you can configure the shortcut Ctrl+Shift+F7 for this script.
OmegaT provides two scripts for checking the translation for untranslated segments. You need to run these scripts one after another.
Finding genuinely untranslated segments
First, you need to run the script called show_untranslated.groovy written by Kos Ivantsov. This will open a window with all untranslated segments. Browse this window to make sure nothing was erroneously left untranslated.
Finding segments with identical source and target
If you enabled the Allow translation to be equal to source option under Options => Editing Behavior, the above script will not show you those potentially erroneous segments that are formally translated, but have the same text in both the source and target part. To find them, you need to run another script called show_same_segments.groovy, also written by Kos. This will open a window with all segments where the translation equals the original.
Running these two scripts before finishing each project is a very good practice, because it may alert you to segments where you removed the translation by accident. It would be a good idea to combine these two scripts into one for greater convenience or, better yet, combine all OmegaT’s quality assurance scripts into one in the future.
Open current file
This indispensable script contributed by Yu Tang opens the file currently active in the Editor pane in its native application instantaneously. For example, if you are translating a DOCX file, by running the script, this file will open in Microsoft Word. This script makes opening the file for reference or making changes very easy.
For other videos about making the most out of OmegaT, visit our YouTube page designed for translators who want to use OmegaT professionally.