Export for bilingual review errors

In theory, export for bilingual review should be a very simple process. Text is copied to a file outside the program, then edited, and copied back into the program. The reality is hardly that simple, because my edition of Trados creates three fictional obstacles to the bilingual review that must be 'solved' before the reimport can be processed:

 

(1) Segment was changed since exporting for bilingual review

(2) Segment contains paragraphs

(3) Cannot merge segments

 

All three errors rarely have to do with the file, but appear in about 90% of bilingual review cases. In order to use bilingual review, I usually have to re-export the file, paste in the changes, then re-import the new file, sometimes repeatedly, or sometimes delete or add tags for issue #3. As one can imagine, this is an extraordinary waste of time. Is there a way to set up Trados bilingual review so that it works like MemoQ? That is, when the import button is used, the text is always copies into the file, 100% of the time, no matter what, and no time-consuming error resolution process is required.

  • Hi ,

    The errors you mention could be very real and it's quite easy to achieve them:

    1. If you open the DOCX with an older version of Word, downsave it to a DOC, use OpenOffice... or something like that
    2. If you press the enter key inside a cell to insert a new line this is in effect creating a new paragraph which is a new segment
    3. The result of one of the above

    Perhaps double check your file and maybe review this article which could be helpful in finding problems:

    multifarious.filkin.com/.../

    The Studio review process does carry some advantages over memoQ but it is more delicate as we use code hidden in the file that can be lost if the file doesn't follow a strict workflow. I can break the memoQ one though... so it's not 100% foolproof.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub