Entries not merging on import in a new MultiTerm 2017 Termbase

Question

I have zero experience in MultiTerm importing, so please forgive my naivety. 
 Back in the days, I was handling all projects for this client in Wordfast Pro and I'd like to migrate it to Studio to stop using WF altogether. 
 Each file is translated from English into Italian and Spanish , so I have an Italian glossary and a Spanish glossary. I'd like to create a multilingual MultiTerm glossary. 
 
 I export each glossary from Wordfast and I get two *.tbx files 
 I then open MultiTerm Convert and convert these *.tbx files into *.xml which I can later import in the TermBase 
 I create a new Multilingual Termbase using MultiTerm 2017 wizard , where I set EN, ES, IT as its languages 
 I import the Spanish glossary in the Termbase. OK 
 I import the Italian glossary in the Termbase... however it duplicates entries as follows: 
 
 Let's suppose the source reads " Dog ". I have two entries: 
 #1 Dog , with the Spanish target Perro and the empty Italian target 
 #2 Dog with just the Italian target reading Cane

If, indeed, I import the Italian termbase first, the situation is the opposite. Why doesn't it merge the entries, so that it reads Dog, Perro, Cane ?

Paul · Accepted Answer

Hi Paola 
 This article might be useful for you: 
 multifarious.filkin.com/.../ 
 But on your specific question, perhaps you'd be better off using the Glossary Converter as this is very good at making the merging process easy: 
 
 I did try to do this using the process you went through and this produced exactly the same result as you... and I don't know why. You do have to use the "Synchronize on Term" option when you process the import but this doesn't seem to work correctly. 
 I'll look at this with the support team, but in the meantime I think you have an easier solution with the Glossary Converter anyway. 
 Regards 
 Paul

Paul · Answer

Hi Paola 
 Unknown said: For the record, it didn't work properly when selecting as input files the Wordfast glossaries (*.txt) directly, but it worked fine when I selected as input files the exported WF glossaries (*.tbx). 
 This is to be expected because the WF txt format is specific to WF and is nothing the GC could know about. 
 Unknown said: Now I am filling in missing terms in MultiTerm (some terms were only in Spanish or Italian, and I'd like that each term to have its equivalent in both languages) but I get a javascript error on merging. 
 Try using the Flags layout instead of the default layout. 
 Regards 
 
 Paul

Trados Studio > 3. MultiTerm

Entries not merging on import in a new MultiTerm 2017 Termbase