One reason that I've noticed I can't click the Apply button is that the glossary contains duplicate entries. Sometimes just duplicate source terms. Maybe check for that and it will give you some joy.

If there are no 100% duplicates, I could see possibly that the plug-in can't tell the difference between some very closely related entries (1. Juni and 10. Juni maybe). Again, maybe someplace to start.

Hello Rowan Smith and Michael Schroeder !

Indeed, the reasons why the button may be disabled are:

1. No terms in the glossary (which is clearly not the case in your instance
2. Invalid terms (target or source is empty)
3. Duplicate terms

We created an item for this to be addressed in the next DeepL version. We'll show a message explaining why the button is disabled and point to the problematic terms.

Emanuel Albu 

Thank you, that will definitely be helpful!

I'm sure there's a better place for it but while I've got you here, could you maybe make it possible for the currently chosen glossary to persist both in a project template as well as when adding the DeepL plug-in to a project? When I add the DeepL plug-in to a project "No glossary" is always selected by default, and it would be nice to have that always remain the last glossary I've selected, or the glossary that is selected within the context of a project template, but it doesn't stick.

Either way, we are very grateful for the terminology functionality of the plug-in

Hi Michael and Emanuel,

Thanks for your ideas. After checking for duplicates and not finding any, I realized that you can also import entries on this interface (rather than pressing on the edit button at the right and importing from the new window that appears, which is what I had been doing above), placing a tick in the memory you want to import into and selecting the icon to the left of the rubbish bin below. So it's all up and running now, thanks to everyone's input.

 Michael Schroeder 

Thank you for pointing that out.

I will add it to the item already created. This will be available in the next version of DeepL.

Rowan Smith 

You're very welcome, but even so, a clear explanation must be given for why the button is disabled. This will be made available in the next DeepL version.