Internal repetitions represent two distinct challenges for translators. You need to make sure they’re translated in the same way across the project. But sometimes, you want to translate them in a different way. In the early days, tackling these two challenges was a nightmare since changing a translation of an internal repetition would require searching and replacing all the occurrences across all the files in a project. The newer programs, OmegaT included, automatically replace each occurrence of an internal repetition, keeping them consistent throughout the entire project, while also allowing unique translations.
Challenge 1: Using auto-propagation in OmegaT
Auto-propagation is a project-specific setting enabled by default. You can confirm this by pressing Ctrl+E and looking for the Auto-propagation of Translations checkbox. To check whether it works correctly, scroll through your project and find any segment that displays in gray. This is a non-unique segment (internal repetition). Translate it, copy the source text, and find it using the Text Search window (Ctrl+F). If you check Display all results, you’ll notice that all the occurrences got translated, not just this one. Whenever you update any of these non-unique segments, the remaining occurrences will update immediately, too. No need to update them individually.
Challenge 2: Alternative translations in OmegaT
But there’s a catch. Some of these internal repetitions will require a different translation depending on the context. For instance, “Title” can mean a title of a document and a person’s title such as “Mr.” Some CAT tools still make dealing with these segments difficult, but with OmegaT, this couldn’t be easier. All you need to do is translate a non-unique segment in a different way, right-click it, and select Create Alternative Translation. When you re-open this segment, the Multiple Translations pane will display two different translations. The alternative translation description in this pane includes the name of the file where it belongs. Because such translations are context-dependent, OmegaT also stores and displays in the pane the source text from the preceding and the following segments. To remove an alternative translation, open the segment, right-click it again, and select Use as Default Translation.
Best practices for alternative translations
- If you have ten occurrences of a repetition, but only one requires an alternative translation, be sure to make this one segment an alternative translation. Don’t leave this segment unique, making the other nine segments alternative translations. I know this sounds common-sense, but it’s not an easy thing to do because as soon as you encounter a repetition that calls for an alternative translation, you’re compelled to change it right away, without thinking whether it might be better to convert the other occurrence. So think before you do this to avoid unnecessary alternative translations.
- Go To Next Untranslated Segment stops where there is at least one alternative translation: You can enable this checkbox in Options => Editing Behavior to make sure each alternative translation opens when you go through the project using Ctrl+U. I keep this option enabled because double-checking these tricky segments is a helpful habit.
- Previously, alternative translations were always file-dependent: OmegaT stored the file name in the project_save.tmx and inserted alternative translations only if the name of the file in the project matched the one in the project_save.tmx. But now, you can configure this behavior by enabling the Ignore file context when identifying segments with alternate translations checkbox under Options → File Filters. I keep this option enabled at all times, because otherwise, something as simple as changing a file name can result in losing alternative translations. The only time you want to disable it is when you have alternative translations with identical context in different files that have to be translated differently.