Jerzy Czopik

You can just drop both Excel files into the Glossary Converter and merge them to create the SDLTB in one go:

EPC EN-DE_merged.zip

This looks ok... so maybe you should go that route?  There are still what looks like duplicates in places but this seems to be related to small differences in the English like these:

Case difference for "Patient"

And in some places there are full stops at the end of one and not the other.  So in general this looks pretty good and only takes a few clicks.

I haven't tried the approach you took yet... but will test later to see if I can understand why your MultiTerm import route didn't work.

Jerzy Czopik

You can just drop both Excel files into the Glossary Converter and merge them to create the SDLTB in one go:

EPC EN-DE_merged.zip

This looks ok... so maybe you should go that route?  There are still what looks like duplicates in places but this seems to be related to small differences in the English like these:

Case difference for "Patient"

And in some places there are full stops at the end of one and not the other.  So in general this looks pretty good and only takes a few clicks.

I haven't tried the approach you took yet... but will test later to see if I can understand why your MultiTerm import route didn't work.

Hi Paul

Glossary Converter does the job properly. But MultiTerm should also be able to merge the two exported XML files. I exported them sorted by English term, then tried to import the second one by English term. In the past this worked (I think last time I did that I used MT 2017). Now both MT 2019 and MT 2021 simply add a second TB into the previous one, duplicating English terms instead of merging them.

Kindest regards

Jerzy

Jerzy Czopik

ok - I've had a quick play with this.  Must admit I would never do it this way... much much longer and more painful... but now that I have I can reproduce the problem you found in 2021.

I then tested in 2017 (didn't bother with 2019.. will take your word for that) and had the exact same problem.  I don't have an older version than this installed... but that's probably irrelevant now anyway.

Having said all of this I can still make it work.  And actually it does a much better job than the Glossary Converter so I may have to rethink my original asessment.  For example, the Glossary Converter does this with nearly duplicates:

Technically correct I guess because it creates new entries for the difference in case.  However, MultiTerm import does this:

And I think this is a neater solution.  Termbase attached:

en-de-gr.zip

The secret to making this work is this (adapting your workflow):

1. GC to convert the two Excel files into separate SDLTB termbases
2. Export both termbases as multiterm XML
3. Create a new en-de-gr termbase in multiterm
4. create an import definition synchronising on the English term
5. import the en-de
6. Now, I deleted the import definition and created it again, and I also ticked the box to run the import at the end
7. this works

The reason it seems to work is that I don't think the import definition is being saved properly.  So when I run it the advanced settings to synchronise on English are omitted.  You can see this in the final screen where you see a summary of what will happen.  When you create the import definition and run it the first time you'll see that summary does mention the synchronisation setting.

So I think the bug is that the definition doesn't save so it can be run as intended afterwards.  I'll log this... but at least you should have a workaround that seems to work.  You should check the result I attached however as I didn't check it thoroughly.

Dear Paul

Many thanks for all your work and confirming the existence of the problem. I have already delivered the results from GC and the customer is OK with that. Nonetheless, I would again go that way.

My process was similar, but after having created a en-ge-gr termbase, I used default import definition, then created a new one to synchronize on English term. And this did not work.