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.

if you restrict under this topic, it is ALWAYS possible using sdltm "directly" without corrupting the SDLTM
you do not have to use "sdltm>tmx>sdltm" detour (and it revealed itself useless if you have fields within it.  -at least very dangerous and tedious)

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.

Hi Paul,

Have this problem, too. and I wondered whether at least I could see the number of found entries so I know how many times I might need to click :-) Or is there way to do it with the batch edit function - i.e. delete the older entries and keep the newer ones or the ones with a certain field value? How would I set this up in the mainenance view? (I'm not much of a workaround person, I prefer to do things directly in SDL..)

1. no way to handle it directly in "SDL" wasy as you wanted

2. if you are 2017 user I have "My workaround" SDL PlugIn for this special case.

Regards 

ah.. never mind, I just read the last line of your comment. You said, You want "SDL only" 

Ok.. everyboady have to have its own idea. Good Luck To You.

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

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.

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.

Thanks, Paul Filkin.

Yeah, ok, seems I'll have no choice but use external tools. I'll give it a try. Pity though, IMHO this TM maintenance is one crucial feature for such tool and should be a tool-inherent thing.