Not Considering

Hi Étienne,

Thanks for raising a new idea to help improve SDL TMS. Translation memories are primarily used in a single language direction only which is why there is only a one-way index create for each language pair. Creating a secondary index to reverse the language direction has a direct impact on the performance of the TM due to the overhead of keeping that index up-to-date with each new segments that is added. If the target language index is required to maintain the TM, I would recommend that you add it using the TM Maintenance tool and then remove it once the maintenance is complete. There are no plans to create the reverse index in SDL TMS. As we converge on a new cloud-based translation memory technology, it's possible that searching for text in the target segments becomes easier.

Regards,

David

Apply systematic two-way indexing when creating TMs showing in TMS

TMs should be created with two-way indexing, meaning that we should always be able to use both F7 and SHIFT+F7 functions to perform global searches in Source and Target sections of TMs opened in TMS TM Maintenance for quick and convivial corrections.

In some instances we can manage by searching in the Source for corrections to be made in Target, but sometimes we're left with the basic CTRL+F function to find content in Target, which might be quite time consuming.

Not sure if double indexation do slow anything (servers, software or else) but I find it very useful to be able to use both F7 and SHIFT+F7 in TMS TM Maintenance.

Thanks

Étienne Morrissette