Victor Linnemann 

I think, if you can't use the Glossary Converter which is definitely the preferred and most reliable method, then you may be able to do this by exporting the MultiTerm XML for the languages you need from MultiTerm.  Then you only have what you need from the start.

Otherwise, if you need to do a lot of this stuff and don't have access to the Glossary Converter, then perhaps look at tools like Excelling MultiTerm from Kaleidoscope:

https://appstore.rws.com/Plugin/185

It may not be the process you want to use but it could be more reliable than manipulating the XML.  There are challenges associated with file manipulation using MultiTerm and MultiTerm Convert, so I would always recommend alternative methods to ensure a smoother user experience.

Why can't you use the Glossary Converter?

Victor, 

I do not fully understand how you tried to split that TDB. 

This is what I did with official EU databases available in the RWS store (they come like in 10-12 languages, sometimes with definitions at language level and NO multimedia),

I exported them fully, applying no filters.

Then I imported the .xml in the existing corporate TDB which has 6 languages. Corresponding terms were automatically taken and imported from the entries available in the EU database and that´s it.

So, in your case, I would create an empty TDB with the structure you need. 

Then export all entries from that megaTDB you have and import the .xml to the new database with fewer languages. 

BUT: I warn you in advance, multimedia files will not be attached properly, so you will have to attach them manually, if any. I guess you have a special folder for those , so it will take time, but not too much.

Definitions may appear readable but locked for editing. No problem. Copy, open a new definition field, paste and delete the automatically created definition.

These are minor failures you may have in the process. But it is quick and easy,

Best regards!

Hello Yulia

Thank you for your helpfull answer. 

OK, now it's clear to me: Defining a custom export instead of trying to filter on default export.

This works fine in the way I want it.

Kind regards

Victor

Hi Paul

I followed Yulia's advice and was able to export only the few languages I wanted. Then imported the XML into an empty SDLTM.

Glossary Converter: I like it very much and often make use of it. It's a gerat tool!

But in some environments I am not allowed to introduce or even use tools that have not been validated.by the company's IT Security.

Thank you for your help.

Kind regards

Victor