Hi Levente Péter Nagy

I use this feature for Multiterm / Studio and it works fine for me. Can you post a couple of screenshots where this issue happens in Studio? This way I can try to reproduce it and maybe help.

Also a screenshot of implied entry in Multiterm so I can see your structure, something like:

In Studio I see:

Almudena

Hi Almudena Ballester,

Thank you for the quick reply.

So, in the meanwhile I have tried all possible variations of ticking and unticking boxes and found out that apparently the order of the picklist items matters. Though I really don't see the logic behind this. 

I have redesigned the picklist so that "forbidden" comes before "allowed", and now it works fine as you can see it on the pictures below.

Can you confirm my assumption on the order of picklist items? I really don't want to inadvertently rely on some hidden setting and get into trouble when working on another computer.

Thanks, Levente

Hi again Levente:

I don't think the order has something to do in this case. I have just the opposite and it works:

I also realized, when configuring the Termbase, that there is no need to mark the "good" translations as preferred or allowed, it is just enough to mark forbidden ones - actually, all other translations in an entry are "allowed" by default. You can spare a lot of field-filling if you have only two categories. 

But you have to be aware of this: if you mark a term as forbidden, Studio will not check the whole entry but just this field. So it can happen that Studio throws an error message for a term which is a mistake as a translation for one term, but it is correct as a translation for another different term.

As an example, let's say that "burdeos" (ES) should be translated as "bordeaux" (PT) and should not be translated as "grená". In the same Termbase, "granate" should be translated as "grená" indeed. Studio will mark as mistakenly translated the word "grená" in target, no matter the source :(

That's really a shortcoming in Studio Terminology Verifier, in my view. Terminology in translation works dually, terms correspond one to each other, term source matches term target. Absolute lists of forbidden words work only partially, maybe to avoid some specific words, rude ones, copyrighted or the like. But concerning terminology verifications, the pair of words must be checked.

So... in your case, "billion"... always will be forbidden. 

Regards,

Almudena

Hi again Levente:

I don't think the order has something to do in this case. I have just the opposite and it works:

I also realized, when configuring the Termbase, that there is no need to mark the "good" translations as preferred or allowed, it is just enough to mark forbidden ones - actually, all other translations in an entry are "allowed" by default. You can spare a lot of field-filling if you have only two categories. 

But you have to be aware of this: if you mark a term as forbidden, Studio will not check the whole entry but just this field. So it can happen that Studio throws an error message for a term which is a mistake as a translation for one term, but it is correct as a translation for another different term.

As an example, let's say that "burdeos" (ES) should be translated as "bordeaux" (PT) and should not be translated as "grená". In the same Termbase, "granate" should be translated as "grená" indeed. Studio will mark as mistakenly translated the word "grená" in target, no matter the source :(

That's really a shortcoming in Studio Terminology Verifier, in my view. Terminology in translation works dually, terms correspond one to each other, term source matches term target. Absolute lists of forbidden words work only partially, maybe to avoid some specific words, rude ones, copyrighted or the like. But concerning terminology verifications, the pair of words must be checked.

So... in your case, "billion"... always will be forbidden. 

Regards,

Almudena

Hi Levente,

I am just a Multiterm/Studio advanced user trying to help & get help in this community :) Just figuring out what the problem could be and giving feedback to developers in order to improve apps and plugins.

Sometimes I know the answer to a question based on my experience, sometimes it is just an approach.

Maybe Luis Lopes could give us a hand here.

Regards,

Almudena

Unknown said:

The Verifier will always throw an error message whenever it finds a forbidden term no matter the source segment...

Hi Levente Péter Nagy and Almudena Ballester 

I reproduced this problem this morning and sent a small package to support.  I'm not sure if this is already something on our list of things to fix but it does look like undesirable behaviour to me.  I'll update you when I have some feedback on this later, if Luis doesn't respond sooner.