Didier Briel wrote:
OmegaT can also read .sdlxliff files. If no translation has been done yet, OmegaT can read them directly. If the translation has started, the Okapi plugin must be used...
I just tried five different existing SDXLIFF files in OmegaT (with the Okapi filter). They opened, and I made a small edit, and then pressed Ctrl+D to generate the target files. Only three of the five target files could be opened by Trados. Two of them looked okay, and the one had some extra segments (that contained no text but only tags) added to the top of the file.
Also, if the SDLXLIFF file contains tracked changes, they will be imported back into Trados as text surrounded by taglike text, and not as tracked changes.
That said, I regularly translate XLIFF files in OmegaT from another source.
Question #2 - is there a feature like Trados's 'pre-translate files' in OmegaT?
OmegaT automatically "pre-translates" everything, provided the TMXs are in the /auto folder of the /tm folder.
Note that if you used "pre-translate" within Trados, and it inserted fuzzy matches into cells, then those cells will be considered "translated" (not "fuzzy") by OmegaT, and the translator will not be able to find those cells, because OmegaT does not show the segment statuses.