Find inconsistencies in a TM

Question

Hi everyone 
 I would like to know if there is a way to find inconsistencies (in target) in a TM (could xbench be of any help??). 
 Any advice is welcome :) 
 Xavier

Paul Filkin · Accepted Answer

Hi Xavier Amouyal 
 You can search for potential duplicates like this: 
 
 Don't enter anything, just select this option and "Perform Search". This will list same source different target results with a separate page for each one.

Paul Filkin · Answer

Yvonne Rezbach 
 I'm afraid the TM Maintenance side of Studio is really poor. You could try using the TM Management utility on the appstore (as Ali mentioned) and this should remove all duplicates retaining only the most recent entry: 
 
 But this is automated and you have no ability to stop, check, base on field values etc. 
 The only other options are external tools like Olifant or Heartsome... or to use something that a developer created which is what Krupa does. Untested however, and he only works with 2017 but you could try it with a copy of your TM if you use 2017. If it doesn't break anything it could save you a lot of time.

Alison Field · Answer

Hi Yvonne Rezbach 
 The best way to attract Paul's attention on a thread that is as old as this is to include an active link with his name... Paul Filkin . This is achieved in his case by typing @ followed immediately with filkin in lower case, no spaces. 
 If you are wishing to eliminate identical duplicates or non-identical duplicates, you can use the following app from the SDL AppStore: 
 SDL Translation Memory Management Utility 
 You can also handle duplicates using Olifant as discussed above. 
 It is also possible to eliminate duplicates simply by exporting a TM to TMX then importing that TMX into a new TM, the duplicates overwrite themselves till there is only one of each if you have the settings correctly adjusted. 
 That may not be what you want to achieve so I'll leave Paul to lend his much greater expertise to replying to you... 
 All the best, 
 Ali

Paul Filkin · Answer

Hi Xavier Amouyal 
 
Do you mean inconsistencies compared to your translation or inconsistencies in your TM itself?

Paul Filkin · Answer

Martin Jornan said: but, if you want to use them (my sdltm has lots, lots of fields) again, you have to make all and every of them "Again" when you import it into SDL Trados Studio. that is pure nonsense. 
 
 This is not really nonsense. The problem with using TMX is that it lists all the fields you used for that TMX but it carries no information about what should actually be in the TM. For example, your TM could be set up for 5 different types of fields and 10 different possible picklist values in each field. The TMX export may not actually contain all the fields or all the values so when you share that TMX with someone else they will not get the same TM as the one you have. 
 Maybe make use of a Language Resource Template and then you will be able to recreate your TMs quickly and reliably? 
 Martin Jornan said: And, Do not mention others age like this, that is dirty attitude. 
 I don't agree with this. TMX is a really old exchange filetype that has been used for decades and it hasn't changed for around a decade. So why wouldn't you use a piece of software that was designed to handle old formats like this if you see fit? I've played a round with Heartsome and it has some good qualities, but I still find Olifant to be more stable than that despite its age. It's still used as part of the Okapi framework by many localization engineers today.

Paul Filkin · Answer

Martin Jornan said: or if you like tmx so much, makes it as "Default". 
 TMX is an exchange file. I didn't say I liked it at all. 
 Martin Jornan said: i really hate to converting something. if you can handle it using sdltm directly do it so. 
 This is not always possible without corrupting the SDLTM. I know you like to work directly with SQL and it is really fast, but it's not always possible to do this safely. It just depends on what you are trying to achieve.

Paul Filkin · Answer

Martin Jornan said: it is ALWAYS possible using sdltm "directly" without corrupting the SDLTM 
 I don't think this is correct. If you are making changes to system and custom fields then yes, it's perfectly fine and we have developed a solution for something we will release shortly that uses SQL to do this as it is very fast. But if you are changing content in the source and/or target segments then it is not always possible. For this we had to use the Language Platform API to prevent corruption of the SDLTM. So we created a mix and match and used SQL where it was safe and the APIs where we needed more surety. 
 I would add a caveat here that this is only a problem for TMs that support the new SDLTM structure to accommodate fragment matching. Legacy TMs are not affected by this, but since we are now on the second version to support fragment matching I think it's safe to say it's risky to use only SQL. The APIs are designed to ensure developers can work on assets safely without damaging them in any way. 
 If you are finding working with SQL is fine for the things you are doing then that's great, but please don't suggest this as always being possible as this may lead some developers down a path to problems.

Trados Studio > 1. Trados Studio

Find inconsistencies in a TM

Top Replies