Under Community Review

Studio behaviour with forbidden terms

We have enabled the check in terminology verify Studio for deprecated terms
When we translate a segment which doesn't contain the source term and we use the deprecated term an error appears corresponding to the line
What we expected was that only in case we had the source term corresponding to the deprecated target the message appeared otherwise lots of fake errors are created.

 
We cannot give for granted that a term deprecated when associated to a term must be considered always deprecated.
Logos Help Desk
Parents

  • I'm for: only flag a forbidden term when the source segment contains the relevant source term. 

    Otherwise, why on earth does the Status (System) contain this status of Forbidden on a language-specific term level? If it does NOT check the source term first, why not simply form a standalone black list for all forbidden terms to avoid them from being used entirely anywhere in the document? 

Comment

  • I'm for: only flag a forbidden term when the source segment contains the relevant source term. 

    Otherwise, why on earth does the Status (System) contain this status of Forbidden on a language-specific term level? If it does NOT check the source term first, why not simply form a standalone black list for all forbidden terms to avoid them from being used entirely anywhere in the document? 

Children
No Data