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

  • Definitely agree. A target term that's defined as a "forbidden" translation of a particular source term is not necessarily forbidden everywhere!
    I can sort of understand why the tool is built this way (if a term really is forbidden, then you don't want it anywhere in your document), so perhaps there needs to be some kind of setting to determine which behaviour the user wants: always flag forbidden terms, or only flag them when the source segment contains the relevant term.

Comment

  • Definitely agree. A target term that's defined as a "forbidden" translation of a particular source term is not necessarily forbidden everywhere!
    I can sort of understand why the tool is built this way (if a term really is forbidden, then you don't want it anywhere in your document), so perhaps there needs to be some kind of setting to determine which behaviour the user wants: always flag forbidden terms, or only flag them when the source segment contains the relevant term.

Children
No Data