Gilles Snoeck 

The best way to do this is probably to correct your TM with the appropriate translation and then rebuild the model for fragment matching.  It might be more efficient to do this by exporting your SDLTM to TMX.  Make the corrections, and then upgrade/import the TMX to a new SDLTM and build the translation model and align the TUs.

The reason this is necessary to take this approach is that the values in the SDLTM used for fragment matching are not stored and used in a simple manner.  Trados Studio relies on precomputed data like hash values, indexes, and fuzzy match scores to speed up the fragment matching process.  These are automatically updated when you make changes within Trados Studio, but if you manually edit the SDLTM file (using a SQLite editor for example), these underlying structures don't get updated correctly.  As a result, your changes might not show up in the fragment matching pane, even though the text has been modified in the database.

By exporting to TMX, you ensure that the system can properly rebuild all the data needed for fragment matching when you import it back as a new SDLTM file.

Gilles Snoeck 

The best way to do this is probably to correct your TM with the appropriate translation and then rebuild the model for fragment matching.  It might be more efficient to do this by exporting your SDLTM to TMX.  Make the corrections, and then upgrade/import the TMX to a new SDLTM and build the translation model and align the TUs.

The reason this is necessary to take this approach is that the values in the SDLTM used for fragment matching are not stored and used in a simple manner.  Trados Studio relies on precomputed data like hash values, indexes, and fuzzy match scores to speed up the fragment matching process.  These are automatically updated when you make changes within Trados Studio, but if you manually edit the SDLTM file (using a SQLite editor for example), these underlying structures don't get updated correctly.  As a result, your changes might not show up in the fragment matching pane, even though the text has been modified in the database.

By exporting to TMX, you ensure that the system can properly rebuild all the data needed for fragment matching when you import it back as a new SDLTM file.

Hum, that’s what I thought, so it’s not possible to do this directly, the only way is to purge the TM from any instance of the bad fragment.

But I don’t think that is feasible since I’m working on a shared TM that belongs to an agency. So I need to convince the project manager to do this instead of me.

Thanks for the explanation !