Cristi Necula

Perhaps ths article makes the resolution a little clearer... same one, just a different layout:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039916

Can you share a screenshot of your Termbase Management View here:

I deliberately addeda sub-language to an existing main language.

If you definitley don't believe you have done any of the things noted in the article you can share your termbase with me and I'll be happy to see if I can find a problem - pfilkin@sdl.com

Hi Paul,

Thank you very much for taking a look at this.

Here is the requested screenshot.

Regarding the point in the article I can confirm as follows:

• your termbase has more than one sub-language for a main language. For example English (United Kingdom) and English (United States). Not applicable

• the XML file you import into the termbase contains for example English (United Kingdom) and English (United States) entries that each have same terms. The distinction from en-GB to en-US is made via a descriptive field in the TBX I was provided with, while the actual languages of the TBX are only 2  and . Therefore I do not think this applies. I have not actually added this descriptive field in the termbase as I do not think it is relevant for the purpose of my test.

• on page Step 3 - Validation Settings of the SDL MultiTerm Desktop/Administrator Import Wizard, the Ignore sub-languages option is ticked/enabled/active. Not applicable

• it was not considered to create a custom import definition to import converted (via SDL MultiTerm Convert) terminology into the existing  Termbase and avoid the import of existing/duplicate terms. Not applicable

Let me know what you think and thank you once again.

Cristi Necula can you share your termbase with me?

Cristi Necula

Thank you for sharing your termbase.  It all looks fine to me, and I don't get any errors.  So, I think you need to check what version of Studio you are running.  Apologies, I should have checked this already.  It's important to have compatible Studio and MultiTerm too.  These are the latest supported versions:

SDL Trados Studio 2019 SR2 - 15.2.5.2145
SDL MultiTerm 2019 - 15.0.5.56289

SDL Trados Studio 2017 SR1 - 14.1.10018.54792
SDL MultiTerm 2017 SR1 - 14.2.8.55461

Hi Paul,

Thanks again for taking a look.

This is very interesting. I have a partial result. I can now run the verification using the batch task function, I have inserted a prohibited term just to verify if everything is working properly and this is the result:

It works !

However, if I actually open the file in the studio editor and run the verification from there I still receive the same error.

This is definitely a step forward as I can use the verification report itself but im still wondering what exactly is going on in the editor.

Thank you again!

Hi Paul,

Thanks again for taking a look.

This is very interesting. I have a partial result. I can now run the verification using the batch task function, I have inserted a prohibited term just to verify if everything is working properly and this is the result:

It works !

However, if I actually open the file in the studio editor and run the verification from there I still receive the same error.

This is definitely a step forward as I can use the verification report itself but im still wondering what exactly is going on in the editor.

Thank you again!