The Trados cloud platform will be undergoing maintenance on Saturday, 9th May 2026 between 05:00 to 17:00 UTC. During this time, you will not be able to log in to the Trados platform.
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 431 subscribers
  • Views 3094 views
  • Users 0 members are here
Options
Related

Retrofit not importing all the changes

Margus Enno

The topic is the Retrofit function - once again. I saw a discussion thread about this here but no useful answer. So, let me ask again: why (what is the logical reason) doesn't Retrofit import all the changes made in the reviewed file?

I even found the following statement in the Retrofit section in the manual for Studio 2017: "Setting the slider to Tolerant, does not necessarily mean that all changes made to the reviewed target document will be imported into the project file". This means that SDL must be aware of this matter. However, on of the points of Studio is that you have the ability to be as accurate as possible - down to the smallest inter-punctuation. Yet here we have a function that, as it seems, does its work in an arbitrary way - some of the changes are being imported, some are not. Why? And what is the algorithm that decides which changes are worth being imported and which left out?

Could anyone explain that - anyone from SDL perhaps?

Margus
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi Margus,
    Retrofit is based on what is referred to as "reverse alignment". Basically the updated native file is aligned with the target language section of the corresponding SDLXLIFF file in the Studio project. So, for unedited segments, the alignment will see no changes and can leave the segments untouched. However, if bigger changes occur, the alignment can no longer be certain if it can accurately update changed segments, as the text might be very different. This can 'throw off' the algorithm when there are a lot of big changes, leading to potentially wrong reverse alignments, changes applied to the wrong segments etc. Which would be bad for the user as the Retrofit process would make the target file worse than it was before running Retrofit, which we are keen to avoid. Against this background the strategy behind Retrofit is conservative. It will only update segments that it is 'certain' about, and if too much text has changed, it cannot do that reliably, and the alignment will go out of sync. So, in order to avoid too many false changes, Retrofit is limited to more confined changes, and is therefore best used when you have small/spot changes in the native target file.
    Hope this helps
    Daniel

    Daniel Brockmann
    Team Trados @ RWS

  • 0 in reply to Daniel Brockmann
    Alright, this is an answer indeed. However, what is also clear from it, is the fact that you need to work on it - hopefully you get it to work as expected by a translator such as myself. Right now, the function is unreliable. But it's good to know, anyway. Thanks.
Reply Children