Hello Trados Community team,
I hope you're doing well.
We recently updated our French Canadian TM (on September 19th) with a file from our translator, but unfortunately, the translation was not of the expected quality. Could you kindly guide me on how we can recover the previous version of the TM before this update?
Thank you in advance for your help!
Virginia
Virginia Seggiaro
The best approach is to correct the document you imported with the good translation and reimport it into your TM.
Or alternatively, but not so accurate:
If it is on a GroupShare server, recover from a SQL backup.
If it is file-based, go back to a previous backup if you have one.
In addition to the advice from Walter Blaser , whose experience exceeds mine by a very long stretch, if you simply want to remove the TUs from a file-based TM (might work for GroupShare, but don't know, never worked with that), open the TM(s) in the TM view of Trados Studio and apply filters such as "Created by", "Last modified by", "Created on" and "Last modified on" to identify the TUs affected. The hitch here is that all you can do is to delete them or mark them (e.g. add a field value). In susequent projects, you can apply penalties based on field values to make these TUs less prominent, if you chose not to delete them in the first place.
But the TM itself does not store versions. so you can't "roll back" to a previous version unless you have an external backup system in place. Personally, I would recommend backing up TMs frequently and keeping a number of versions, like creating a daily, a weekly and a monthly backup, all of which are stored on a physical device other than the TMs you are actively working with. Again, not sure how this could be done with server-based TMs.
Daniel
In addition to the advice from Walter Blaser , whose experience exceeds mine by a very long stretch, if you simply want to remove the TUs from a file-based TM (might work for GroupShare, but don't know, never worked with that), open the TM(s) in the TM view of Trados Studio and apply filters such as "Created by", "Last modified by", "Created on" and "Last modified on" to identify the TUs affected. The hitch here is that all you can do is to delete them or mark them (e.g. add a field value). In susequent projects, you can apply penalties based on field values to make these TUs less prominent, if you chose not to delete them in the first place.
But the TM itself does not store versions. so you can't "roll back" to a previous version unless you have an external backup system in place. Personally, I would recommend backing up TMs frequently and keeping a number of versions, like creating a daily, a weekly and a monthly backup, all of which are stored on a physical device other than the TMs you are actively working with. Again, not sure how this could be done with server-based TMs.
Daniel
Virginia Seggiaro
The suggestions from Daniel Hug are another way to correct the situation, and it is good to point out these possibilities you have in TM management.
In your case, importing the "corrected" document into the TM has the big advantage that this will automatically overwrite the segments which contain the bad translations, and you don't need to search for them. For this to happen, you need to select this option for the import process:
And yes, TMs do not store versions and the advice to periodically make backups is an excellent suggestion. The easiest way to create backups is to export the TM to a TMX file. This has two advantages: (1) the files are much smaller than the SDLTM file and "corruption resistent" because they are text files and (2) you can always use them to recreate a "broken" TM. This is true both for file-based as for server-based TMs.
Translate
