#Trados xliff editor update#

Let me suggest that you send your project to the OmegaT developers and/or that you redo your tests with: 'Insert all tags' instead of 'Insert source' and that you validate your tags before target creation. It's hard for me to believe that the first time you review OmegaT with a trivial DOCX file you manage to bump into the one little file that triggers the bug that nobody had noticed yet. The XLIFF filter has been used by quite a number of users already, on plenty of real life SDLXLIFF files and such behavior was never reported. My idea is that you probably had the 'Insert source' default setting on and that you erased the while translating, then you forgot to validate the tags and you created a malformated XLIFF file.Īs for 'trashing tags on the source side', I find that a bit suspicious. How have you inserted the 2 other tags ? Have you inserted them manually? Have you used the 'Insert tags' function? Have you used the 'Insert source' function?Īlso, have you validated the tags before creating the target ? Your screenshot shows one thing: the tag is missing from your target segment. I am really surprised by the results you obtained in OmegaT. The file from SDL Trados Studio looks as follows in the memoQ environment: I have translated many SDLXLIFF files in memoQ and seldom encountered a problem of any kind. The target file from the SDLXLIFF translated with OmegaT was fine. The matter is being pursued with Kilgray support. Either there is a problem with the version I have installed (5.0.56) or the installation is corrupted.

Careful, systematic testing revealed, however, that the roundtrip of a bilingual XLF file from memoQ back into memoQ failed. But the problem with the XLF file from memoQ was frighteningly repeatable.

However, as astute observers have noted, I probably deleted the missing tag when editing in OmegaT, and a subsequent successful re-test of the workflow confirmed this.

#Trados xliff editor update#

In a similar test with an XLIFF from memoQ, the version of OmegaT I tested (version 2.3.0, update 3) appeared to trash even more tags, and the target file was completely reformatted! In fact, it even trashed tags on the source side in the memoQ file! Thus I was deeply concerned about the XLIFF filter in OmegaT. So, I opened it again from said folder).One of the tags in the second segment was dropped. So, if you have never saved CTRL+S (or from the menu File > Save or Save all (guessing, my Studio runs in German) your project is saved in the SDL Studio 20XX folder, but not in the Studio list (AFAIK, it has happened to me before, Studio froze and I had to close it before saving the opened file in the editor. Save as target file means only that you 'export' the translation, you create the translation file in the original format, say a MSWord file if the original file was a MSWord file. I keep separate folders per each client and an updated copy on server. As to the TM, how can you tell it was last updated on May 10th?! I wouldn't know straight away.

(I hope you haven't re-imported the project otherwise your progress is gone, but Studio always asks you whether you want to import an older version while you are at it). If your project is there (appears as a folder) you can open it from there double-clicking it. If not sure, mouse-over on one of your projects and you'll see the path Have you checked in the folder where all Studio projects are saved? Normally, it is created automatically under user > Documents > SDL Studio 20XX > Projects (path varies according to how you named your 'user' and your Studio version).