![]() OmegaT: Best practice for translating content from.Clean up the tag mess with CodeZapper for all CAT.SDL Trados Studio: Translating memoQ bilingual RTF.Wordfast Pro: Translating memoQ bilingual RTF tables.For the most part I am referring to the greater number of filters. In general, though, I would like to comment that I like the improvements to the tool compared to what I saw several years ago. So at the moment I can't make a definitive statement confirming or recanting my comments here about OmegaT and XLIFF. On days like this I wish I had done the work on a virtual machine. I have reported this to Kilgray support and await feedback from there before continuing my tests. ![]() Either there is a bug in the current filter or my own configuration has been trashed in testing. when I did a roundtrip test from my copy of memoQ I discovered that memoQ trashes the roundtrip import of its own XLIFF file. I've spent the afternoon re-testing in various configurations, and the problem with memoQ described elsewhere at least is repeatable (I haven't had the time to look at Studio yet in the test matrix.) The tags were indeed trashed when the XLF file translated in OmegaT was re-imported to memoQ version 5.0.56 (which had generated it). Thank you for the comments, Jean-Christophe. I don't doubt your sincerity but I think you may have forgotten a few important things while you translated. I've used OmegaT numerous times for quite complex SDLXLIFF file sets that were produced by the client on Studio 2009 and Studio 2011, either as standalone XLIFF files, or as files that I extracted from translation packages with Started 2011 and none of the files I delivered triggered a negative reaction from the client (or from the software).Īfter I acquired a license for Starter 2011, all the files were checked in OmegaT before verification in Starter 2011 and "return package" creation and none shown the behavior you describe. 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. 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. One of the tags in the second segment was dropped.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |