QA for forbidden terms

Question

Hi there, 
 I want QA to check if million is not translated as billion in any segment. 
 I added the term to my TB marking its correct equivalent as "Right" and the prohibited term as "Wrong" choosing from the picklist attributes I preset for this descriptive field. 
 In the Terminology Verifier I ticked the checkbox "Check for terms which may have been set as forbidden" and selected "Wrong" as forbidden value (and left "Right" unchecked). 
 Now, the QA runs and throws an error message for all the segments where million or billion is used, even if used correctly (i.e. with the term marked as "Right"). 
 Any idea? Thanks, Levente

Levente Péter Nagy · Accepted Answer

Hello Hayley, 
 To use Norah's solution follow these steps: 
 Options > Verification > QA Checker 3.0 > Regular Expressions 
 
 Check "Search regular expressions" Description: Give a friendly name to the RegEx pattern RegEx source: Add source segment term RegEx target: Add forbidden target segment term Condition: "Report if both target and source RegEx patterns match" Check "Ignore case" Action: "Add item" 
 You can add as many patterns as you want. 
 The above RegEx pattern tells QA Checker to trigger a warning when "milli&oacute;" appears in the source segment and "billion" in the target one. It does the job, although it will also (erroneously) flag segments where both "million" and "billion" appear (correctly), but this is quite rare and I can live with it. 
 Also, try to experiment with the options in the Conditions dropdown list! 
 Best, 
 Levente

Almudena Ballester · Answer

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&aacute;". In the same Termbase, "granate" should be translated as "gren&aacute;" indeed. Studio will mark as mistakenly translated the word "gren&aacute;" 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

Nora Díaz · Answer

Hi Levente, 
 
As a workaround to get those segments flagged, you could set up a regex QA check where you set billion as the source and its undesired (wrong) translation as the target and tell Studio to flag any segments where that combination is used.

Anthony Rudd · Answer

The regex pattern can be extended to prevent the problem when "million" and "billion" are both present, by adding a negative lookahead (posit the absence of the correct term). 
 (?!.*million)^.*billion But as you mention, this effort might not be "cost-effective".

Paul · Answer

Hi Levente Péter Nagy , 
 
I just moved your post into the MultiTerm forum but it just occurred to me that perhaps you have used the Language Cloud (Beta) for your termbase? If you have then I think this is probably why the verification doesn't work as I don't think this is supported with the Language Cloud Terminology solution.

Paul · Answer

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.

Almudena Ballester · Answer

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

Trados Studio > 3. MultiTerm

QA for forbidden terms

Top Replies