100% match from NMT is not auto-propagating

Hi,

I am wondering why 100% match from NMT is not auto-propagating. 

The one below is only a one little example (pic 1). I can come up with dozens. Like this one, which is a telephone number. When I confirm the segment (pic nr 2) the segments which are below (probbably 50 segments more as this document has dozens of pages).. the only segment that fills out is the next one and it does not even confirms automatically.

Is this normal ? Should it be like this? I dont understand why this, and many other segments like this, will not auto-propagate - once they are confirmed once and for all they should be included in MT and give 100% match next time (like the ones that are green)? or not? why is this match over ang over again coming from NMT and not from MT.

Is there any explanation for this? BTW I have TS 2019. Is NMTs working better in later versions.?

Screenshot of Trados Studio showing a list of segments with 100% NMT matches, including a telephone number not auto-propagating.

Screenshot of Trados Studio with a confirmed segment and subsequent segments not auto-filled or confirmed automatically.

My project settings look like this, btw:

Screenshot of Trados Studio project settings displaying translation memory and machine translation configurations.



Generated Image Alt-Text
[edited by: Trados AI at 12:33 PM (GMT 0) on 29 Feb 2024]
emoji
Parents
  • Hello,

    It seems like you're experiencing an issue with auto-propagation of 100% matches from Neural Machine Translation (NMT) in Trados Studio 2019. This could be due to a few reasons.

    Step 1: Check your settings. Ensure that you have the 'Auto-propagate exact matches to confirmed segments' option enabled in your project settings. This should allow 100% matches to be auto-propagated.

    Step 2: Understand the nature of NMT. NMT does not store translations like a traditional Translation Memory (TM) does. Instead, it generates translations on-the-fly based on the input it receives. This means that even if a segment is confirmed once, it won't necessarily give a 100% match the next time because the NMT is not 'remembering' the translation.

    Step 3: Consider upgrading your Trados Studio version. While Trados Studio 2019 does support NMT, newer versions may have improved functionality and better integration with NMT providers.

    Step 4: If you're still experiencing issues, it might be worth considering using a traditional TM for segments that you want to auto-propagate. This way, once a segment is confirmed, it will be stored in the TM and should give a 100% match the next time it appears.

    Remember, NMT is a tool to assist with translation and may not always behave in the same way as a traditional TM. It's always a good idea to review all translations, whether they come from a TM or NMT, to ensure accuracy.

    I hope this helps clarify things for you. If you have any other questions, feel free to ask.

    Best regards,

    RWS Community AI

    emoji
  • Hi Trados AI,

    All this sounds logical. I have correct settings for auto progation, Step 4 "This way, once a segment is confirmed, it will be stored in the TM and should give a 100% match the next time it appears." - How do I do this? Is it not enought that I confirm the match that comes from NMT and the MT is updated with it? I dont get why after confirming NMT match TS insist on using NMT next time exactly on the same segment and NOT MT.   Should I just disable NMT? 

    emoji
  • Hello, I have the same issue after upgrading Studio 2021 to the latest version BUT without using NMT. I have this one project where there are plenty of files in each package with a huge TM and my own local TMs. Normally in the 2021 version, I was able to confirm the many 100% matches and CM segments by clicking "pre-translate" and "confirm 100% matches". It stopped doing this entirely, meaning regardless if I try to batch process all files in the project or just a single one. It is also not showing me "Translated" segments in the project view when it should show me many of those. 
    I have gone through all the steps you have previously discussed and it makes no difference whatsoever. It is simply not doing this. The files are analyzed correctly where I can see the matches and 100% and CM correctly. When I open the files, those segments are pre-filled and labelled 100% or CM. It is quite a manual task to confirm them all by hand and also the project is more stable when I do the pre-translate step. I am at a total loss why that is. I thought before that maybe it was something with the files themselves but that is not the case. And: it all worked fine up until the upgrade.
    I just did a test using the old 2021 version, where everything was "normal" and it pre-translated. Then I reopened that package in the 2022 version of Studio and I had the same problem again. I don't understand this.
    Does anyone have new insights?
    Thanks!

    emoji
Reply
  • Hello, I have the same issue after upgrading Studio 2021 to the latest version BUT without using NMT. I have this one project where there are plenty of files in each package with a huge TM and my own local TMs. Normally in the 2021 version, I was able to confirm the many 100% matches and CM segments by clicking "pre-translate" and "confirm 100% matches". It stopped doing this entirely, meaning regardless if I try to batch process all files in the project or just a single one. It is also not showing me "Translated" segments in the project view when it should show me many of those. 
    I have gone through all the steps you have previously discussed and it makes no difference whatsoever. It is simply not doing this. The files are analyzed correctly where I can see the matches and 100% and CM correctly. When I open the files, those segments are pre-filled and labelled 100% or CM. It is quite a manual task to confirm them all by hand and also the project is more stable when I do the pre-translate step. I am at a total loss why that is. I thought before that maybe it was something with the files themselves but that is not the case. And: it all worked fine up until the upgrade.
    I just did a test using the old 2021 version, where everything was "normal" and it pre-translated. Then I reopened that package in the 2022 version of Studio and I had the same problem again. I don't understand this.
    Does anyone have new insights?
    Thanks!

    emoji
Children