Term recognition fails in next segment after end of context match propagation

Hi Folks,

Issue as described, Studio version 17.1.6.16252.

Slightly specific sequence of events, but here goes.

If:

  1. ...Studio has just propagated some Context Matches
  2. ...and ends up on a new segment with no matches of any kind, i.e. it cannot do a partial match and so populate the segment in some way
  3. ...and this segment has terms in it that are in the termbase

Then:

  1. ...Studio will show the term matches for the last segment with a propagated context match
  2. ...and will not show the correct term matches for the current segment

Anyone experienced this? This is 100% replicable in this document.

Weirdly, it does NOT happen after:

  • Propagating a 100% match
  • In any segment where Studio can do something like suggest a partial match

It's only for segments after a context match propagation where Studoi found nothing it could offer.

Any ideas?

Thx,

Ed



Added tags.
[edited by: Edward Bradburn at 3:40 PM (GMT 1) on 27 Sep 2023]
emoji
  • Hello Ed,

    I understand your concern about the term recognition issue in Trados Studio. This seems to be a specific sequence of events that leads to this issue.

    Here are a few steps you can try to resolve this:

    Step 1: Ensure that your Trados Studio is updated to the latest version. You can check for updates within the application.

    Step 2: Try to clear the cache in Trados Studio. You can do this by going to "File" > "Setup" > "Options" > "Editor" > "Automation" and then uncheck "Enable AutoSuggest". Click "OK" and then restart Trados Studio. After restarting, you can go back to the same settings and re-enable "AutoSuggest".

    Step 3: If the issue persists, you might want to consider re-indexing your termbase. This can be done by going to "Termbases" > "Reorganize Termbase".

    Step 4: If none of the above steps work, you might want to consider creating a new project and importing your files there to see if the issue persists.

    Please note that these are general troubleshooting steps and might not work in all cases. If the issue still persists, it might be a bug in the software and you might have to wait for the next update for a fix.

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

    Best regards,

    RWS Community AI

    emoji
  •  

    I had to fiddle around a bit to reproduce it, but I seem to be able to confirm your findings.  I guess if you turn off the automatic confirmation of an autopropagated match you won't have this problem because you'll always have to manually confirm the AP segments, and then this doesn't happen.

    I'm not sure if this has been logged but I'll raise it with the support team and let you know.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Hi Paul,

    Many thanks.

    However, I do like the automatic confirmation of autopropagated matches from the TM, something that Studio does very well.

    So in all, I'm still saving time here. I just need to be a bit careful after Studio has had an autopropagate spree, so to speak.

    Thanks for confirming you'll raise the issue, would be great to have it fixed.

    emoji