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

Yes, I want my consultaion

Video: Get More Efficient with Alternative Translations in XLIFF (Translation Software OmegaT 3.1.1 Review. Part 1)

This video is the first part of the free translation software OmegaT 3.1.1 review.

Using trans-unit ID as identifier of alternative translations in the XLIFF filter

Previously, OmegaT identified alternative translations of non-unique segments by their preceding and next segments; that is, their context. This is not always accurate enough, though, because the contexts can be identical, while the translations still need to be different. Now OmegaT adds trans-unit ID as such identifier for XLIFF files. You can choose between the Previous and next paragraphs and trans-unit ID in the XLIFF filter options. This new option makes identifying segments in those rare cases more accurate. Note that it is available for the native XLIFF filter only. And remember that unlike the Previous and next paragraphs option, this new option will result in losing all alternative translations should the trans-unit IDs change in source XLIFF files, e.g., after you or the client make changes to those files.

Moving several files in the Project Files window

You can now move several files at once when arranging their order in the Project Files window. This is helpful when you need to move, say, 20 files together.

Regular spaces can also match non-breaking spaces in search.

Previously, when you searched for several words separated by regular spaces, OmegaT did not find the same words, but with non-breaking spaces between them. This could be quite frustrating, for example, when you were making changes globally and missed occurrences with non-breaking spaces. Now by enabling the Space matches nbsp checkbox in the Text Search window, you get all results regardless of whether they include regular or non-breaking spaces.

Sorting by column in the Spellchecker window

If your language uses letters different from that of the original language, you can now conveniently sort the spell checking results and have all potential errors in your language display at the end of the window. For example, if you translate from English into Russian and keep many English words in the translation, those words will come up as spell-checking errors as well, and you will have yo go through a mixed list of English and Russian words. But if you sort by column, all Russian words will appear at the end of the window, allowing you to ignore all English words falsely flagged as errors.

The main QA script now finds untranslated and source=target segments.

Previously, these two error types were available by running separate scripts only. Integrating them in the main QA script makes it much easier to check for these errors. You do not need to remember to run those scripts separately each time.

Downloading the free translation software OmegaT

Get the new version of OmegaT now.

If this blog helped you in some way, please share a link to this post on your site or through social media.

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.