Segments found in TM appear with AT status

Hello users,

I have recently started to work with SDL Trados Studio 2015 and now I have encountered a problem I cannot manage to solve.


I am translating a document with quite a big Translation Memory (50 MB). When I go segment by segment, there appear two segments that have a 90% and a 100% fuzzy match with the TM respectively, however they have the status of AT.

There are several issues that worry me:

1) Why do they have the status of Automated Translation?

2) Plus, if I run the batch task "Populate Translation Memories" these two segments do not appear in the resulting Translation Memory. Why do not they appear?

3) When I go segment by segment, all the segments that have a fuzzy match with the TM appear directly in the Editor Window so you don't have to write it. However, this does not happen with these two segments. Does anyone have any idea of why this may happen?

I would really appreciate it so I can understand what is going on with my translation.

Thank you very much.

Best,
Ona.

  • Hi ,

    Unknown said:
    1) Why do they have the status of Automated Translation?

    I have come across this before, usually because the TU was createded after it was translated with Machine Translation.  The origin gets saved into the TM.  I can replicate this in one scenario only:

    1. Pretranslate your file with MT

    2. Now all segments should have AT status but are not confirmed

    3. Update the TM using a batch task and update all the segment, confirmed or not

    4. Detach the MT engine and you should see the TM results come though with the AT status

    Maybe this is how your TM was created?

    Unknown said:
    2) Plus, if I run the batch task "Populate Translation Memories" these two segments do not appear in the resulting Translation Memory. Why do not they appear?

    Have you confirmed them first, or made sure you update unconfirmed segments too.  I can't see the status of your TUs in the screenshot.

    Unknown said:
    3) When I go segment by segment, all the segments that have a fuzzy match with the TM appear directly in the Editor Window so you don't have to write it. However, this does not happen with these two segments. Does anyone have any idea of why this may happen?

    I believe this is because the origin is AT, but I don't know if it's deliberate or a bug.  I'll have to check this with the development team.

    Regards

    Paul

    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

  • Hi Paul,

    I'm having the same problem that Ona is having and it is very persistent in the files I'm working on. I have re-translated a few VSDX files a number of times now using a TM that I know contains dozens of items that are displayed as AT after the re-translation. It seems as though the AT is stronger than the TM matches, even CM matches! Below is a screenshot of one of the instances but there are dozens more in two small files. It is a very worrying phenomenon, as it has occurred several times in recent months. We have Studio 2019 now, but it also occurred when we had 2017 until recently. 

    Hope you can help!

    Kind regards,

     

    Joël 

    Interlingo