SLD Trados 2019 is still incapable of properly importing reviewed bilingual files... but is this a feature?

Dear All,

The latest version of Trados 2019 (SDLTrados Studio 2019 SR1 - 15.1.3.55768) still suffers from the same shortcomings that countless previous iterations have suffered from. Namely, it does not import correctly a reviewed bilingual file.

Translated segments are still empty in the Editor after the import, although they are clearly translated in the bilingual file. Then I have to manually copy the translated segments from the bilingual file into Trados Editor, which wastes me a tone of time and frankly drives me crazy.

But...

I am starting to think that this might be a feature rather than a bug (as some Trados proponents used to say back in the day).

I have noticed today that Trados correctly imports all segments that had had at least some translated text present (even a single word) before the export, but imports none of the segments that were completely empty (no translation whatsoever) before the export and were then translated from 0% to 100%.

Let us take a look...

This is how the bilingual file ready for import looks:

Screenshot showing a bilingual file with two segments, one marked as Draft (0%) and the other as Not Translated (0%), with translations present in the target column.

And this is what Trados actually imports:

Screenshot of Trados Studio Editor with the same segments showing no translations imported, indicated by the absence of text in the target column.

So, could this be a lapse of logic on the part of SDL software engineers, rather than a software bug?

Here is the thing though: exporting for bilingual review and then re-importing the translated bilingual file is an essential part of my workflow when I outsource translations to linguists who do not work with Trados. And I am hardly the exception. So, whatever the reason, this bug or lack of functionality needs to be fixed quickly once and for all.

Best regards,

Pavel Tsvetkov



Generated Image Alt-Text
[edited by: Trados AI at 9:12 PM (GMT 0) on 28 Feb 2024]
emoji
Parents Reply
  • Please, note that none of the other CAT tools acts in the same way when importing reviewed files.

    That's irrelevant really.  Other CAT tools use a different mechanism to us which is more robust.  We support track changes in the word file for this process and we use hidden metadata in each segment.  All of this is what makes the process prone to problems when the files are not handled carefully.

    Whe the feature was first delivered it was done so on the basis of "light review" and was never intended to be used for the purpose you, and probably many others, use it for.  In fact there was a lot of resistance to doing it at all because the approach we have always taken is one of more control by keeping things in the CAT tool workflow.

    just wondering why no one at Trados has thought of this previously?

    They have... but like I said, this just isn't the Trados way of working so offerring flexibility to do complete translation work outside of Studio in a Word file has never been a priority.  It's seen as a review tool and that's it.

    Imagine all the time wasted by thousands of translators copying text manually from the translated bilingual file into Trados Editor over the years... mind boggling.

    Indeed... but why are they doing this?  Understanding the way things work is key to doing anything, and as long as you copy the source to target first, don't change the format of the Word file, and especially don't introduce hard returns into the file, then you shouldn't have a problem.

    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

Children
No Data