Are you tasked with translating SDLXLIFF files from an agency client, but want to use OmegaT to do the translation? This may happen when you do not own a SDL Trados Studio license or you, like some of our readers, have an aversion to this program. Here is the good news: OmegaT makes such task easy with the use of the XLIFF filter included in the Okapi plugin. In fact, this filter has been around for a few years, but it is only with the M26 release that it can save translated SDLXLIFFs properly, without breaking them.
How to use the Okapi XLIFF filter
- Put the SDLXLIFF files into the source folder of your OmegaT project.
- Open the project, then open the project properties and go to File Filters.
- NEWER VERSIONS: Make sure the SDL-XLIFF files (Okapi) filter is checked while the XLIFF (native) filter is unchecked. OmegaT will highlight the current filter for your convenience.
- OLDER VERSIONS: Make sure the XLIFF files (Okapi) filter is checked while the XLIFF (native) filter is unchecked. Go to Edit for that filter to add the source filename pattern: *.sdlxliff.
- In the project properties, uncheck Enable Sentence-level segmenting. By disabling segmentation, you keep the original segmentation of SDLXLIFF files and also enable OmegaT to insert any 100% matches automatically.
- Translate the text.
- Create the translated files.
Although this is absolutely the easiest way to translate SDLXLIFF files in OmegaT, I cannot promise it is the safest one. I did test it extensively and found no problems so far. However, I stongly recommend a roundtrip. Before diving deep in translation, you translate a few segments, save the “translated” file, and open it in SDL Trados Studio to make sure everything is fine.
It is also a good idea to open translated files in Studio after completing translation. Obviously, to do this kind of check, you need to own a Studio license. If you do not have one, at least have a colleague who has such a license and can check files for you in important projects.
You may also want to use this route with files that have a lot of 100% matches, because there is no easy way to handle such files with the native XLIFF filter.
If this blog post helped you, you can help it in return—share a link to it on your site or social media profile. You can also watch other OmegaT videos we posted.