Dear Sotir:

All you have to do is create as many example fields as languages you manage, and tell the program which one goes under which language - at Term level, not Index level. 

So, I recomend you to use an excel to make an structure and then convert it with Multiterm convert. This way, while converting you can select those fields and dependencies.

In my example:

I have different descriptive fields (note-language) which I send under desired Term for every language. You will obtain and .xdt file - a definition file you can reuse for further updates.

Also, if you have this structure in you Multiterm, you can manually add examples by editing the entry and filling the correspondent field under the language term.

I hope I could help,

Almudena

What do you mean by "goes to the correct language automatically"? For a massive conversion? Almudena is right, you have to prepare a well-structured excel and then import. However, after that, are you planning to keep saving your terms in a file and then importing to multiterm? In my opinion, it is better to manage the entries in the database directly.

Hi Sotir, I'm not quite sure what your use case is. Do you create a new termbase, or add to an existing one? And in what format is the data you want to add?

Hello, Almudena!

It looks like my problem was caused by the incorrect order of my fields in Excel. I followed your advice and rearranged the structure, then added another example field for my second language, which solved the issue.

Thank you for your help!