You are currently working on UAT 

Project TM not containing any fuzzies and less 100% matches than analysis

Hi,

When generating a new project, the Project TM nor the sdlxliff seem to contain all the fuzzies and the 100% matches that the analysis shows.

FYI: Until recently I worked with two versions of Studio simultaneously: I generated my projects and analysis with Studio 2011 and did the reviewing and translating part in Studio 2017. Two days ago however, I noticed that Studio 2011 gave an incomplete match (less than 25% 100 matches) for a text that had already been entirely translated, whereas Studio 2017 gave a 100% match... so I had to conclude that something has been blocked and that these analysis /projects are no longer trustworthy since they do not seem to include the latest updates. Hence I decided not to use 2011 any longer and to switch to 2017 for everything. Not ideally, since 2017 is very slow lately so this will most likely be very time-consuming (another problem I would like to solve).

I now switched entirely to 2017 only to notice that some of the 100% segments remain empty and that none of the fuzzies are proposed in the projects I create. Earlier I had already noticed that even 99% matches were not proposed automatically when translating, I had to retrieve these through Concordance Search… 

What is going wrong? The TM does no longer function as a TM if that is the case...

I already checked all the necessary settings: TU recognition is at 65% now (previously 70%), the TM updates automatically but on top of that I always perform a manual update through Batch tasks after reviewing the translation as well.

I also tried not to produce a Project TM, but the sdlxliff remains entirely empty in that case.

What else can I try? Any ideas, suggestions are most welcome!

Regards,

 

Ann

PS. Below you see two analysis: the one I made with Studio 2017 and the one my collegue made with an earlier version of Studio and the same project TM and source text

19-213VNLFR AG.xlsx ...Analyse 19-213VNLFR.xlsx

 

Parents Reply
  • Hi again Ann,

    TM compatibility might be the problem. See the description below for the "TM Compatibility Plug-in for SDL Trados Studio 2015":

    Screenshot of TM Compatibility Plug-in for SDL Trados Studio 2015 webpage, highlighting the issue with TM leverage when using Studio 2017 TMs in Studio 2015 and the solution to reindex TMs.

     

    So, it appears that using a Studio 2017 TM in Studio 2015 will "adversely affect" leverage.

    The Studio app is only available for Studio 2015, but the description says that "reindexing those TMs in Studio 2015 restores normal leverage".

    If your colleague reindexes the Project TM you sent her, it might restore her leverage. (It is worth a try, anyway :-)

    Best regards,
    Bruce Campbell
    ASAP Language Services

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 4:06 PM (GMT 0) on 28 Feb 2024]
Children