• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 1516 views
  • Users 0 members are here
Options
Related

Different Target in Translation Memory

Giannis Ouzounis

Hello everyone,

I have an issue in Studio/TM for a project I am working on.

After creating a Studio project, usually some segments have translations from TM, but I found out that in some segments, there are different entries from TM and in TM message, it says "Different Target in Translation Memory". Even though these segments are different from TM, it's locked (I set up the studio to lock for CM during pre-translation) with CM status.

In the end, a segment which is different from TM is locked and set to CM.

Is this something to do with my Studio settings? Could you please check how I can avoid this and simply use the TM?

I attached one image.

Screenshot of Trados Studio showing a segment with a warning 'Different target in translation memory.' The segment is locked and marked as CM, despite having different entries from the TM.

Generated Image Alt-Text
[edited by: Trados AI at 10:15 AM (GMT 0) on 29 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi ,

    First I think the TM project settings has not penalties. This would explain why you get 100 % matches when there are tag differences. Please check your settings here:

    Trados Studio project settings showing penalties for missing and different formatting, multiple translations, auto-localization, text replacement, and alignment.

    From my point of view, a small formatting penalty (such as 1) makes sense.

    Now, to explain the locked segments, I think you have this configuration in the Pre-translate task:

    Trados Studio batch processing settings with Pre-translate settings showing options for minimum match value, translation overwrite mode, and confirming and locking matches.

    Could you please check it as well?
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 10:15 AM (GMT 0) on 29 Feb 2024]
  • 0 in reply to Jesús Prieto

    Dear Jesús,

    Thank you for looking into this.

    The penalty settings in the project are exactly you show. The pre-translate options as well, with Lock context matches.

    I agree that there would be a high fuzzy match for the TU without the tags, and the other match should have been chosen.

    Next, I did two tests: First, I unlocked everything in my file, I ran a Pre-translate with Overwrite existing translation if better match found, but it didn't fix the issue. Still, the translation without the tags was there. Then, I tried to Clear Target Segment in the whole file, and pre-translate again. This time the correct TU was picked up.

    I have no idea why it happened this way. A colleague of mine actually created the project, but I still tested everything on this specific project without changing any of the existing settings. Could the cause be a difference in Studio version? 
    emoji